CVE-2013-6356 DO NOT USE THIS CANDIDATE NUMBER.
Not scored
Published
Updated
Check this codebase for CVE-2013-6356 and fix it if it is affected.
What it is: CVE-2013-6356 is a vulnerability, published on 9 Dec 2013.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6356 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-2013-6356/ (Markdown: https://insights.sbomify.com/CVE-2013-6356/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2013-6356?
CVE-2013-6356 is a vulnerability, published on 9 Dec 2013.
Official description
DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue because of dependency on the victim's direct involvement in modifying the Windows registry to enable the attack. Notes: none
Which versions are affected by CVE-2013-6356?
How do I fix CVE-2013-6356?
No fix has been published for CVE-2013-6356 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-6356 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6356 exists.
Public exploit code: 2 Exploit-DB entries.