Vulnerabilities · 2018 · Npmjs
CVE-2018-7408
Npmjs Npm vulnerability
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 products
Npm. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Npmjs Npm runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- blog.npmjs.org/post/171169301000/v571 · Vendor Advisory
- github.com/npm/npm/commit/74e149da6efe6ed89477faa81fef08eee7999ad0 · Third Party Advisory
- github.com/npm/npm/issues/19883 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2018-7408
- cve.org/CVERecord?id=CVE-2018-7408
More vulnerabilities in Npmjs products
CVE-2022-29244CVE-2021-43616CVE-2021-39135CVE-2021-39134CVE-2021-37713CVE-2021-37712CVE-2021-37701CVE-2021-23362All 15
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.