CVE-2014-9297 DO NOT USE THIS CANDIDATE NUMBER.
Not scored
Published
Updated
Check this codebase for CVE-2014-9297 and fix it if it is affected.
What it is: CVE-2014-9297 is a vulnerability, published on 4 Oct 2015.
Exploitation: There is no known exploitation of CVE-2014-9297 in the wild and no public exploit code.
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-2014-9297/ (Markdown: https://insights.sbomify.com/CVE-2014-9297/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2014-9297?
CVE-2014-9297 is a vulnerability, published on 4 Oct 2015.
Official description
DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2014-9750, CVE-2014-9751. Reason: this ID was intended for one issue, but was associated with two issues. Notes: All CVE users should consult CVE-2014-9750 and CVE-2014-9751 to identify the ID or IDs of interest. All references and descriptions in this candidate have been removed to prevent accidental usage
Which versions are affected by CVE-2014-9297?
How do I fix CVE-2014-9297?
Upgrade to a fixed version.
Is CVE-2014-9297 being exploited?
There is no known exploitation of CVE-2014-9297 in the wild and no public exploit code.
Sources
Also known as UBUNTU-CVE-2014-9297.