Skip to main content

Supply Chain Attack - NPM

Description

NPM dependencies do not have a software integrity definition file to use, allowing third party actors to change or inject malicious software.

Impact

Override dependencies or component with malicious content.

Recommendation

Pin your version numbers in package.json Use a package-lock.json and install with npm ci

Threat

Anonymous attacker from Internet with write access to the provider releases.

Expected Remediation Time

⌚ 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 madurity: 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

Compliant code

All docker dependencies are pinned using secure mechanisms


Non compliant code

There are docker dependencies not pinned


Requirements

Fixes

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.