Code execution via unclaimed Python dependency
Published Aug 23, 2021 · Updated Aug 4, 2024
Dependency confusion in NVIDIA Caffe before 0.17.4 allows remote attackers to execute code when a user installs Python requirements. The Python requirements list names gfortran as a PyPI dependency although no such distribution existed, allowing an attacker-controlled package to satisfy the unverified name. Exploitation requires an attacker to claim that name on PyPI and a user to install the affected requirements, which executes the package's installation code.
Summary
What happened
Dependency confusion in NVIDIA Caffe before 0.17.4 allows remote attackers to execute code when a user installs Python requirements. The Python requirements list names gfortran as a PyPI dependency although no such distribution existed, allowing an attacker-controlled package to satisfy the unverified name. Exploitation requires an attacker to claim that name on PyPI and a user to install the affected requirements, which executes the package's installation code.
The record
- CVE
- CVE-2021-39158
- Published
- Aug 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA Caffe
- Classifications
- CWE-345, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 0.17.4
What conditions does exploitation require?
What is affected?
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