410 – Dependency Confusion
Description
The application incorrectly defines the dependencies to be used. This generates some ambiguity that can be used by an attacker to confuse the package manager in charge of installing or updating the project's dependencies, with the aim of executing potentially harmful code, thus increasing the possible attack vectors.
Impact
- Execute malicious code in the application - Deploy a malicious version of the application that can lead to a system unavailability
Recommendation
- Set the name of the organization that owns the private dependency in the package manager file. - Set the organization in both the private and public registry of the package manager.
Threat
Anonymous attacker from the Internet
Expected Remediation Time
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: N
- Attack complexity: H
- Attack Requirements: N
- Privileges required: N
- User interaction: P
- Confidentiality (VC): L
- Integrity (VI): L
- Availability (VA): L
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
- Exploit maturity: P