CVE-2018-7408
published 2018-02-22CVE-2018-7408: An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm"…
PriorityP434high7.8CVSS 3.0
AVLACLPRLUINSUCHIHAH
EPSS
0.33%
25.1th percentile
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | npm | — | — |
| npmjs | npm | — | — |
| npmjs | npm | >= 0 < 5.7.1 | 5.7.1 |
CVSS provenance
nvdv3.07.8HIGHCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvdv2.04.6MEDIUMAV:L/AC:L/Au:N/C:P/I:P/A:P
vendor_debian7.8LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Incorrect Permission Assignment for Critical Resource in NPM
osv·2022-05-13
CVE-2018-7408 [HIGH] Incorrect Permission Assignment for Critical Resource in NPM
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
GHSA
Incorrect Permission Assignment for Critical Resource in NPM
ghsa·2022-05-13
CVE-2018-7408 [HIGH] CWE-732 Incorrect Permission Assignment for Critical Resource in NPM
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Debian
CVE-2018-7408: npm - An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next:...
vendor_debian·2018·CVSS 7.8
CVE-2018-7408 [HIGH] CVE-2018-7408: npm - An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next:...
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved
sid: resolved
trixie: resolved
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
http://blog.npmjs.org/post/171169301000/v571https://github.com/npm/npm/commit/74e149da6efe6ed89477faa81fef08eee7999ad0https://github.com/npm/npm/issues/19883http://blog.npmjs.org/post/171169301000/v571https://github.com/npm/npm/commit/74e149da6efe6ed89477faa81fef08eee7999ad0https://github.com/npm/npm/issues/19883
2018-02-22
Published