https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 12 Oct 2026 20:02:42 +0000 https://cve.radiocsirt.org/vuln/ghsa-3cv2-h65g-fgmm <p><strong>Affected:</strong> crates.io: astral-tokio-tar</p> <p>### Impact</p> <p>Versions of astral-tokio-tar prior to 0.6.2 contain a PAX header interpretation bug that allows manipulated entries to be made selectively visible or invisible during extraction with astral-tokio-tar versus other tar implementations. An attacker could use this differential to smuggle unexpected files onto a victim&#39;s filesystem.</p> <p>### Details</p> <p>When a tar stream contains multiple &#34;header&#34; entries prior to a file entry, astral-tokio-tar applies the PAX header (`x`) to the next entry in the stream, regardless of type. For example, a stream of `x -&gt; L -&gt; file` (PAX, GNU longname, file) would result in `x`&#39;s extensions being applied to `L` rather than to `file`.</p> <p>[Per POSIX pax](https://pubs.opengroup.org/onlinepubs/9799919799/utilities/pax.html), this is incorrect: a PAX header always applies to a file entry, not any intermediary entries. See the &#34;pax Header Block&#34; section for the specific prescription there.</p> <p>As a result of this, an attacker can contrive a tar containing a sequence of tar headers such that astral-tokio-tar applies the PAX header&#39;s size extension to the next header in sequence, effectively desynchronizing the stream and enabling astral-tokio-tar specific skippage/extraction of members. In other words, a file can be contrived to extract differently on astral-tokio-tar than on other tar parsers.</p> <p>### Patches</p> <p>Versions 0.6.2 and newer of astral-tokio-tar address this differential.</p> <p>### Workarounds</p> <p>Users are advised to upgrade to version 0.6.1 or newer to…</p> <p><strong>Affected:</strong> crates.io: astral-tokio-tar</p> <p>### Impact</p> <p>Versions of astral-tokio-tar prior to 0.6.2 contain a PAX header interpretation bug that allows manipulated entries to be made selectively visible or invisible during extraction with astral-tokio-tar versus other tar implementations. An attacker could use this differential to smuggle unexpected files onto a victim&#39;s filesystem.</p> <p>### Details</p> <p>When a tar stream contains multiple &#34;header&#34; entries prior to a file entry, astral-tokio-tar applies the PAX header (`x`) to the next entry in the stream, regardless of type. For example, a stream of `x -&gt; L -&gt; file` (PAX, GNU longname, file) would result in `x`&#39;s extensions being applied to `L` rather than to `file`.</p> <p>[Per POSIX pax](https://pubs.opengroup.org/onlinepubs/9799919799/utilities/pax.html), this is incorrect: a PAX header always applies to a file entry, not any intermediary entries. See the &#34;pax Header Block&#34; section for the specific prescription there.</p> <p>As a result of this, an attacker can contrive a tar containing a sequence of tar headers such that astral-tokio-tar applies the PAX header&#39;s size extension to the next header in sequence, effectively desynchronizing the stream and enabling astral-tokio-tar specific skippage/extraction of members. In other words, a file can be contrived to extract differently on astral-tokio-tar than on other tar parsers.</p> <p>### Patches</p> <p>Versions 0.6.2 and newer of astral-tokio-tar address this differential.</p> <p>### Workarounds</p> <p>Users are advised to upgrade to version 0.6.1 or newer to…</p> https://cve.radiocsirt.org/vuln/ghsa-3cv2-h65g-fgmm