CVE-2018-7408
Last modified
CVE-2018-7408 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.33% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Npmjs | Npm | 5.7.0 |
References
- http://blog.npmjs.org/post/171169301000/v571Vendor Advisory
- https://github.com/npm/npm/commit/74e149da6efe6ed89477faa81fef08eee7999ad0Third Party Advisory
- https://github.com/npm/npm/issues/19883Issue Tracking, Third Party Advisory
- http://blog.npmjs.org/post/171169301000/v571Vendor Advisory
- https://github.com/npm/npm/commit/74e149da6efe6ed89477faa81fef08eee7999ad0Third Party Advisory
- https://github.com/npm/npm/issues/19883Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-7408?
How severe is CVE-2018-7408?
How do I fix CVE-2018-7408?
Are you affected by CVE-2018-7408?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
