Supply Chain Attack - Lock Files
Description
A lock file has not been defined to validate the integrity of the software to be used. This can lead to a supply chain attack if the software is compromised, such as by injecting malware.
Impact
Override dependencies or component with malicious content.
Recommendation
Set the version numbers in your administrator file and make use of the lock file where the complete software tree used by the project is defined and where it has integrity data defined for each software used.
Threat
Anonymous attacker from Internet with write access to the provider releases.
Expected Remediation Time
⌚ 15 minutes.
Score
Default score using CVSS 3.1. It may change depending on the context of the src.
Base
- Attack vector: N
- Attack complexity: H
- Privileges required: N
- User interaction: R
- Scope: U
- Confidentiality: N
- Integrity: L
- Availability: N
Temporal
- Exploit code maturity: U
- Remediation level: O
- Report confidence: R
Result
- Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N/E:U/RL:O/RC:R
- Score:
- Base: 3.1
- Temporal: 2.6
- Severity:
- Base: Low
- Temporal: Low
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): N
- Integrity (VI): L
- Availability (VA): N
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
- Exploit maturity: U
Result 4.0
- Vector string: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
- Score:
- CVSS-BT: 0.6
- Severity:
- CVSS-BT: Low
Compliant code
All package.json files are also committed with their respective package-lock.json, yarn.lock or equivalents for other package managers.
Non compliant code
A project that uses a package.json file without also including the lock file in version control.
Requirements
Fixes
