| Package | Affected versions | Patched versions |
|---|---|---|
| sdk | ≤ 1.1.0.20≤ 1.2.0.10≤ 4.4.1.0 | |
| node.js | = 0.10.0= 0.10.1= 0.10.10= 0.10.11= 0.10.12= 0.10.13= 0.10.14= 0.10.15= 0.10.16= 0.10.16-isaacs-manual= 0.10.17= 0.10.18= 0.10.19= 0.10.2= 0.10.20= 0.10.21= 0.10.22= 0.10.23= 0.10.24= 0.10.25= 0.10.26= 0.10.27= 0.10.28= 0.10.29= 0.10.3= 0.10.30= 0.10.31= 0.10.32= 0.10.33= 0.10.34= 0.10.35= 0.10.36= 0.10.37= 0.10.38= 0.10.39= 0.10.4= 0.10.40= 0.10.41= 0.10.5= 0.10.6= 0.10.7= 0.10.8= 0.10.9= 0.12.0= 0.12.1= 0.12.2= 0.12.3= 0.12.4= 0.12.5= 0.12.6= 0.12.7= 0.12.8= 0.12.9= 4.0.0= 4.1.0= 4.1.1= 4.1.2= 4.2.0= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 4.2.5= 4.2.6= 4.3.0= 4.3.1= 4.3.2= 4.4.0= 4.4.1= 5.0.0= 5.1.0= 5.1.1= 5.2.0= 5.3.0= 5.4.0= 5.4.1= 5.5.0= 5.6.0= 5.7.0= 5.7.1= 5.8.0= 5.8.1= 5.9.0= 5.9.1 | |
| npm | ≥ 3.0.0, < 3.8.3< 2.15.1 | 3.8.32.15.1 |
| npm | ≥ 3.0.0, < 3.8.3< 2.15.1 | 3.8.32.15.1 |
Affected versions of the npm package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry.
An attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token.
This compromised token could be used to do anything that the user could do, including publishing new packages.
npm install npm@latest -gRunning one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free