Source-code tampering via unverified SSH host keys
Published Jan 11, 2023 · Updated Mar 10, 2025
Authentication failure in Rust Project Cargo 0.67.0 and earlier allows man-in-the-middle attackers to alter SSH-fetched source code. Cargo's built-in Git transport accepts an SSH server's public key without comparing it against trusted host keys when cloning indexes or dependencies. Exploitation requires an SSH-based fetch, including HTTPS-to-SSH URL rewrites, and a network position that can intercept the connection.
Summary
What happened
Authentication failure in Rust Project Cargo 0.67.0 and earlier allows man-in-the-middle attackers to alter SSH-fetched source code. Cargo's built-in Git transport accepts an SSH server's public key without comparing it against trusted host keys when cloning indexes or dependencies. Exploitation requires an SSH-based fetch, including HTTPS-to-SSH URL rewrites, and a network position that can intercept the connection.
The record
- CVE
- CVE-2022-46176
- Published
- Jan 11, 2023
- Updated
- Mar 10, 2025
- Vendor
- Rust Project
- Product
- Cargo
- Classifications
- CWE-347, CWE-322, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2023CVE publishedPublication date reported by the CVE source.
- Mar 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 0.67.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo