CVE-2009-2030 Unspecified vulnerability in the XML Digital Signature verification functionality in JVA-RUN in JDK 6.0 in IBM OS/400 i5/OS V5R4M0 and V6R1M
Critical 10.0
Published
Updated
Check this codebase for CVE-2009-2030 and fix it if it is affected.
What it is: CVE-2009-2030 is a critical vulnerability in Sun Jdk, published on 11 Jun 2009.
Exploitation: There is no known exploitation of CVE-2009-2030 in the wild and no public exploit code.
Affected product: Sun Jdk. 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-2009-2030/ (Markdown: https://insights.sbomify.com/CVE-2009-2030/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2009-2030?
CVE-2009-2030 is a critical vulnerability in Sun Jdk, published on 11 Jun 2009.
Official description
Unspecified vulnerability in the XML Digital Signature verification functionality in JVA-RUN in JDK 6.0 in IBM OS/400 i5/OS V5R4M0 and V6R1M0 has unknown impact and attack vectors related to "XML SECURITY PATCH."
Which versions are affected by CVE-2009-2030?
It affects 2 products.
Products include Ibm Os\/400, Sun Jdk.
How do I fix CVE-2009-2030?
No fix has been published for CVE-2009-2030 yet. Limit exposure of the affected software until one is available.
Is CVE-2009-2030 being exploited?
There is no known exploitation of CVE-2009-2030 in the wild and no public exploit code.
Sources
Also known as GHSA-9frm-mf75-f6q2.