CVE-2017-1000000 DO NOT USE THIS CANDIDATE NUMBER.
Not scored
Published
Updated
Check this codebase for CVE-2017-1000000 and fix it if it is affected.
What it is: CVE-2017-1000000 is a vulnerability, published on 19 Feb 2019.
Exploitation: There is no known exploitation of CVE-2017-1000000 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-2017-1000000/ (Markdown: https://insights.sbomify.com/CVE-2017-1000000/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2017-1000000?
CVE-2017-1000000 is a vulnerability, published on 19 Feb 2019.
Official description
DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. This issue lacks details and cannot be determined if it is a security issue or not. Notes: none
Which versions are affected by CVE-2017-1000000?
How do I fix CVE-2017-1000000?
No fix has been published for CVE-2017-1000000 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-1000000 being exploited?
There is no known exploitation of CVE-2017-1000000 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.