Code execution via public dependency substitution
Published Nov 12, 2021 · Updated Aug 3, 2024
Dependency confusion in Antilles before 1.0.1 allows remote attackers to execute code when a user installs affected components. Four component requirements.txt files named the unpublished antilles-tools dependency without restricting resolution to an Antilles-controlled source. Exploitation requires an attacker-controlled package to win dependency resolution and a user to install the affected software, after which package installation executes attacker-supplied code.
Summary
What happened
Dependency confusion in Antilles before 1.0.1 allows remote attackers to execute code when a user installs affected components. Four component requirements.txt files named the unpublished antilles-tools dependency without restricting resolution to an Antilles-controlled source. Exploitation requires an attacker-controlled package to win dependency resolution and a user to install the affected software, after which package installation executes attacker-supplied code.
The record
- CVE
- CVE-2021-3840
- Published
- Nov 12, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-427, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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