CVE-2002-0192 DO NOT USE THIS CANDIDATE NUMBER.
Not scored
Published
Updated
Check this codebase for CVE-2002-0192 and fix it if it is affected.
What it is: CVE-2002-0192 is a vulnerability, published on 17 May 2002.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0192 exists.
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-2002-0192/ (Markdown: https://insights.sbomify.com/CVE-2002-0192/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2002-0192?
CVE-2002-0192 is a vulnerability, published on 17 May 2002.
Official description
DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2002-0193, CVE-2002-1564. Reason: This candidate was published with a description that identified a different vulnerability than what was identified in the original authoritative reference. Notes: Consult CVE-2002-0193 or CVE-2002-1564 to find the identifier for the proper issue
Which versions are affected by CVE-2002-0192?
How do I fix CVE-2002-0192?
No fix has been published for CVE-2002-0192 yet. Limit exposure of the affected software until one is available.
Is CVE-2002-0192 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0192 exists.
Public exploit code: 1 Exploit-DB entry.