VulnerableCode Package Details - pkg:cargo/cargo@0.67.0

Search for packages

Vulnerability	Summary	Fixed by
VCID-n4fu-fzu3-sbex Aliases: CVE-2022-46176 GHSA-r5w3-xm58-jv6j	Cargo did not verify SSH host keys The Rust Security Response WG was notified that Cargo did not perform SSH host key verification when cloning indexes and dependencies via SSH. An attacker could exploit this to perform man-in-the-middle (MITM) attacks. This vulnerability has been assigned CVE-2022-46176. ## Overview When an SSH client establishes communication with a server, to prevent MITM attacks the client should check whether it already communicated with that server in the past and what the server's public key was back then. If the key changed since the last connection, the connection must be aborted as a MITM attack is likely taking place. It was discovered that Cargo never implemented such checks, and performed no validation on the server's public key, leaving Cargo users vulnerable to MITM attacks. ## Affected Versions All Rust versions containing Cargo before 1.66.1 are vulnerable (prior to 0.67.1 for the crates.io package). Note that even if you don't explicitly use SSH for alternate registry indexes or crate dependencies, you might be affected by this vulnerability if you have configured git to replace HTTPS connections to GitHub with SSH (through git's [`url.<base>.insteadOf`][1] setting), as that'd cause you to clone the crates.io index through SSH. ## Mitigations We will be releasing Rust 1.66.1 today, 2023-01-10, changing Cargo to check the SSH host key and abort the connection if the server's public key is not already trusted. We recommend everyone to upgrade as soon as possible. Patch files for Rust 1.66.0 are also available [here][2] for custom-built toolchains. For the time being Cargo will not ask the user whether to trust a server's public key during the first connection. Instead, Cargo will show an error message detailing how to add that public key to the list of trusted keys. Note that this might break your automated builds if the hosts you clone dependencies or indexes from are not already trusted. If you can't upgrade to Rust 1.66.1 yet, we recommend configuring Cargo to use the `git` CLI instead of its built-in git support. That way, all git network operations will be performed by the `git` CLI, which is not affected by this vulnerability. You can do so by adding this snippet to your [Cargo configuration file](https://doc.rust-lang.org/cargo/reference/config.html): ```toml [net] git-fetch-with-cli = true ``` ## Acknowledgments Thanks to the Julia Security Team for disclosing this to us according to our [security policy][3]! We also want to thank the members of the Rust project who contributed to fixing this issue. Thanks to Eric Huss and Weihang Lo for writing and reviewing the patch, Pietro Albini for coordinating the disclosure and writing this advisory, and Josh Stone, Josh Triplett and Jacob Finkelman for advising during the disclosure. [1]: https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf [2]: https://github.com/rust-lang/wg-security-response/tree/main/patches/CVE-2022-46176 [3]: https://www.rust-lang.org/policies/security	0.67.1 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-n4fu-fzu3-sbex
Aliases:
CVE-2022-46176
GHSA-r5w3-xm58-jv6j

Cargo did not verify SSH host keys The Rust Security Response WG was notified that Cargo did not perform SSH host key verification when cloning indexes and dependencies via SSH. An attacker could exploit this to perform man-in-the-middle (MITM) attacks. This vulnerability has been assigned CVE-2022-46176. ## Overview When an SSH client establishes communication with a server, to prevent MITM attacks the client should check whether it already communicated with that server in the past and what the server's public key was back then. If the key changed since the last connection, the connection must be aborted as a MITM attack is likely taking place. It was discovered that Cargo never implemented such checks, and performed no validation on the server's public key, leaving Cargo users vulnerable to MITM attacks. ## Affected Versions All Rust versions containing Cargo before 1.66.1 are vulnerable (prior to 0.67.1 for the crates.io package). Note that even if you don't explicitly use SSH for alternate registry indexes or crate dependencies, you might be affected by this vulnerability if you have configured git to replace HTTPS connections to GitHub with SSH (through git's [`url.<base>.insteadOf`][1] setting), as that'd cause you to clone the crates.io index through SSH. ## Mitigations We will be releasing Rust 1.66.1 today, 2023-01-10, changing Cargo to check the SSH host key and abort the connection if the server's public key is not already trusted. We recommend everyone to upgrade as soon as possible. Patch files for Rust 1.66.0 are also available [here][2] for custom-built toolchains. For the time being Cargo will not ask the user whether to trust a server's public key during the first connection. Instead, Cargo will show an error message detailing how to add that public key to the list of trusted keys. Note that this might break your automated builds if the hosts you clone dependencies or indexes from are not already trusted. If you can't upgrade to Rust 1.66.1 yet, we recommend configuring Cargo to use the `git` CLI instead of its built-in git support. That way, all git network operations will be performed by the `git` CLI, which is not affected by this vulnerability. You can do so by adding this snippet to your [Cargo configuration file](https://doc.rust-lang.org/cargo/reference/config.html): ```toml [net] git-fetch-with-cli = true ``` ## Acknowledgments Thanks to the Julia Security Team for disclosing this to us according to our [security policy][3]! We also want to thank the members of the Rust project who contributed to fixing this issue. Thanks to Eric Huss and Weihang Lo for writing and reviewing the patch, Pietro Albini for coordinating the disclosure and writing this advisory, and Josh Stone, Josh Triplett and Jacob Finkelman for advising during the disclosure. [1]: https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf [2]: https://github.com/rust-lang/wg-security-response/tree/main/patches/CVE-2022-46176 [3]: https://www.rust-lang.org/policies/security

0.67.1
Affected by 0 other vulnerabilities.

Vulnerability	Summary	Aliases
VCID-r9ky-9nbm-yucw	Multiple vulnerabilities have been discovered in Rust, the worst of which could result in denial of service.	CVE-2022-36113 GHSA-rfj2-q3h3-hm5j
VCID-ssct-y25y-3qbw	Multiple vulnerabilities have been discovered in Rust, the worst of which could result in denial of service.	CVE-2022-36114 GHSA-2hvr-h6gw-qrxp

Vulnerability

Summary

Aliases

VCID-r9ky-9nbm-yucw

Multiple vulnerabilities have been discovered in Rust, the worst of which could result in denial of service.

CVE-2022-36113
GHSA-rfj2-q3h3-hm5j

VCID-ssct-y25y-3qbw

Multiple vulnerabilities have been discovered in Rust, the worst of which could result in denial of service.

CVE-2022-36114
GHSA-2hvr-h6gw-qrxp

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-04-02T16:58:45.078531+00:00	GHSA Importer	Affected by	VCID-n4fu-fzu3-sbex	https://github.com/advisories/GHSA-r5w3-xm58-jv6j	38.1.0
2026-04-01T16:03:10.015214+00:00	GHSA Importer	Fixing	VCID-r9ky-9nbm-yucw	https://github.com/advisories/GHSA-rfj2-q3h3-hm5j	38.0.0
2026-04-01T16:03:09.981955+00:00	GHSA Importer	Fixing	VCID-ssct-y25y-3qbw	https://github.com/advisories/GHSA-2hvr-h6gw-qrxp	38.0.0