Arbitrary code execution via unverified repository snapshots
Published Jan 12, 2024 · Updated Jun 3, 2025
Cryptographic signature bypass in Gentoo Portage before 3.0.47 allows man-in-the-middle attackers to inject code into the package tree. The standalone emerge-webrsync utility downloads a .gpgsig file for the repository snapshot but installs the snapshot without verifying that signature. Exposure requires use of emerge-webrsync and an attacker positioned to alter its download; other Portage synchronization methods are not affected.
Summary
What happened
Cryptographic signature bypass in Gentoo Portage before 3.0.47 allows man-in-the-middle attackers to inject code into the package tree. The standalone emerge-webrsync utility downloads a .gpgsig file for the repository snapshot but installs the snapshot without verifying that signature. Exposure requires use of emerge-webrsync and an attacker positioned to alter its download; other Portage synchronization methods are not affected.
The record
- CVE
- CVE-2016-20021
- Published
- Jan 12, 2024
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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