dbcve.org
JavaApplication · Ibm

CVE-2013-3009

HIGH · 9.3 CVSS v2.0 Published 2013-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The com.ibm.CORBA.iiop.ClientDelegate class in IBM Java 1.4.2 before 1.4.2 SR13-FP18, 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 improperly exposes the invoke method of the java.lang.reflect.Method class, which allows remote attackers to call setSecurityManager and bypass a sandbox protection mechanism via vectors related to the AccessController doPrivileged block.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The com.ibm.CORBA.iiop.ClientDelegate class in IBM Java improperly exposes the invoke method of java.lang.reflect.Method, allowing remote attackers to bypass the Java sandbox by calling setSecurityManager through the AccessController doPrivileged block.

MitigationUpgrade IBM Java to version 1.4.2 SR13-FP18, 5.0 SR16-FP3, 6 SR14, 6.0.1 SR6, 7 SR5 or later to remediate this sandbox bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JavaApplication
Affected:= 1.4.2= 1.4.2.13= 1.4.2.13.1= 1.4.2.13.2= 1.4.2.13.3= 1.4.2.13.4= 1.4.2.13.5= 1.4.2.13.6= 1.4.2.13.7= 1.4.2.13.8= 1.4.2.13.9= 1.4.2.13.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Java installation
    Run 'java -version' and check for IBM Java (not Oracle/OpenJDK). On Windows check the installation directory for IBM patterns.
    Affected if The system is not running IBM Java, only IBM Java versions in the 1.4.2 through 1.4.2.13.10 range are affected.
  2. Determine the exact IBM Java version
    Run 'java -version 2>&1' or check the release file in the Java installation directory for the full version string like 1.4.2, 1.4.2.13, 1.4.2.13.5, etc.
    Affected if The version matches 1.4.2, 1.4.2.13, 1.4.2.13.1, 1.4.2.13.2, 1.4.2.13.3, 1.4.2.13.4, 1.4.2.13.5, 1.4.2.13.6, 1.4.2.13.7, 1.4.2.13.8, 1.4.2.13.9, or 1.4.2.13.10.
  3. Check Java Security Manager configuration
    Inspect any application configurations or startup scripts that set a custom Security Manager via System.setSecurityManager or the -securty Java flag.
    Affected if The flaw allows bypass of the Security Manager, but the vulnerability exists regardless of whether a custom Security Manager is configured; the presence of the com.ibm.CORBA.iiop.ClientDelegate class in the IBM Java runtime is the trigger.

You are affected if IBM Java version 1.4.2 through 1.4.2.13.10 is installed and the com.ibm.CORBA.iiop.ClientDelegate class is present in the runtime.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade IBM Java to version 1.4.2 SR13-FP18, 5.0 SR16-FP3, 6 SR14, 6.0.1 SR6, 7 SR5 or later to remediate this sandbox bypass vulnerability.

Recommended fix High confidence

IBM Java 1.4.2 SR13-FP18 (or later 1.4.2.x release)

  1. Confirm current IBM Java version by running 'java -version' or checking the installation
  2. Download IBM Java 1.4.2 SR13-FP18 (or later 1.4.2.x release) from IBM Fix Central or official IBM distribution channels
  3. Backup any critical applications and configuration files dependent on the current Java installation
  4. Install the upgraded IBM Java 1.4.2 SR13-FP18 or later version
  5. Update JAVA_HOME environment variable to point to the new installation path if necessary
  6. Restart any running applications to ensure they use the new Java runtime
  7. Verify the fix by confirming the com.ibm.CORBA.iiop.ClientDelegate class no longer improperly exposes the Method.invoke() method
Caveat IBM Java 1.4.2 is an end-of-life legacy product; consider migrating to a supported Java version (IBM Java 7 or 8) as part of a broader modernization effort

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Java Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-3009 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data