CVE-2017-14849 Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the p
High 7.5
Published
Updated
Check this codebase for CVE-2017-14849 and fix it if it is affected.
What it is: CVE-2017-14849 is a high-severity vulnerability in Nodejs Node.js, published on 28 Sep 2017.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-14849 exists.
Affected product: Nodejs Node.js. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2017-14849/ (Markdown: https://insights.sbomify.com/CVE-2017-14849/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2017-14849?
CVE-2017-14849 is a high-severity vulnerability in Nodejs Node.js, published on 28 Sep 2017.
Official description
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the pathname validation used by unspecified community modules.
Weakness: CWE-22
Which versions are affected by CVE-2017-14849?
It affects 1 product.
Products include Nodejs Node.js.
How do I fix CVE-2017-14849?
Upgrade to a fixed version.
Is CVE-2017-14849 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-14849 exists.
Public exploit code: 1 Nuclei template and 1 proofs of concept on GitHub.
Other vulnerabilities in Nodejs Node.js
Sources
Also known as GHSA-c5w2-4jcq-rvf5.