<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 16:41:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-38497 — Cargo not respecting umask when extracting crate archives</title>
      <link>https://db.gcve.eu/vuln/cve-2023-38497</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rust-lang cargo&lt;/p&gt;
&lt;p&gt;Cargo downloads the Rust project’s dependencies and compiles the project. Cargo prior to version 0.72.2, bundled with Rust prior to version 1.71.1, did not respect the umask when extracting crate archives on UNIX-like systems. If the user downloaded a crate containing files writeable by any local user, another local user could exploit this to change the source code compiled and executed by the current user. To prevent existing cached extractions from being exploitable, the Cargo binary version 0.72.2 included in Rust 1.71.1 or later will purge caches generated by older Cargo versions automatically. As a workaround, configure one&amp;#39;s system to prevent other local users from accessing the Cargo directory, usually located in `~/.cargo`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rust-lang cargo&lt;/p&gt;
&lt;p&gt;Cargo downloads the Rust project’s dependencies and compiles the project. Cargo prior to version 0.72.2, bundled with Rust prior to version 1.71.1, did not respect the umask when extracting crate archives on UNIX-like systems. If the user downloaded a crate containing files writeable by any local user, another local user could exploit this to change the source code compiled and executed by the current user. To prevent existing cached extractions from being exploitable, the Cargo binary version 0.72.2 included in Rust 1.71.1 or later will purge caches generated by older Cargo versions automatically. As a workaround, configure one&amp;#39;s system to prevent other local users from accessing the Cargo directory, usually located in `~/.cargo`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2023-38497</guid>
    </item>
    <item>
      <title>USN-6275-1 — cargo, rust-cargo vulnerability</title>
      <link>https://db.gcve.eu/vuln/usn-6275-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: cargo, Ubuntu:Pro:18.04:LTS: cargo, Ubuntu:Pro:20.04:LTS: cargo, Ubuntu:Pro:22.04:LTS: cargo, Ubuntu:Pro:22.04:LTS: rust-cargo&lt;/p&gt;
&lt;p&gt;Addison Crump discovered that Cargo incorrectly set file permissions
on UNIX-like systems when extracting crate archives. If the crate would
contain files writable by any user, a local attacker could possibly use
this issue to execute code as another user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: cargo, Ubuntu:Pro:18.04:LTS: cargo, Ubuntu:Pro:20.04:LTS: cargo, Ubuntu:Pro:22.04:LTS: cargo, Ubuntu:Pro:22.04:LTS: rust-cargo&lt;/p&gt;
&lt;p&gt;Addison Crump discovered that Cargo incorrectly set file permissions
on UNIX-like systems when extracting crate archives. If the crate would
contain files writable by any user, a local attacker could possibly use
this issue to execute code as another user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-6275-1</guid>
    </item>
  </channel>
</rss>
