JavaApplication · Ibm

CVE-2013-3012

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

NVD · unedited

Unspecified vulnerability in the Java Runtime Environment (JRE) 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 allows remote attackers to affect confidentiality, availability, and integrity via unknown vectors, a different vulnerability than CVE-2013-3009 and CVE-2013-3011.

Technical summary

dbcve analysis · moderate confidence

Unspecified vulnerability in IBM Java Runtime Environment affecting versions 1.4.2 before SR13-FP18, 5.0 before SR16-FP3, 6 before SR14, 6.0.1 before SR6, and 7 before SR5. The vulnerability allows remote attackers to affect confidentiality, availability, and integrity with unknown attack vectors.

MitigationUpgrade affected IBM Java installations to the specified fixed versions (1.4.2 SR13-FP18, 5.0 SR16-FP3, 6 SR14, 6.0.1 SR6, or 7 SR5 or later) or migrate to supported Java versions.

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

Affected products & versions

NVD · CPE data

JavaApplication

Affected:= 5.0.0.0= 5.0.11.0= 5.0.11.1= 5.0.11.2= 5.0.12.0= 5.0.12.1= 5.0.12.2= 5.0.12.3= 5.0.12.4= 5.0.12.5= 5.0.13.0= 5.0.14.0

CVSS breakdown

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?

dbcve checks

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

Check installed IBM Java version

Run 'java -version' from the command line. IBM Java typically displays version info in the format: JRE version "1.X.X" where X represents the version number. Also check for 'IBM' or 'J9' in the output.

Affected if The displayed version shows IBM Java and falls within: 1.4.2 before SR13-FP18, 5.0 before SR16-FP3, 6 before SR14, 6.0.1 before SR6, or 7 before SR5.
Verify vendor is IBM

Review the java -version output for 'IBM' or 'J9' to confirm this is IBM Java, not Oracle Java or OpenJDK. IBM Java uses 'IBM J9' in its version string.

Affected if The output contains 'IBM' or 'IBM J9' indicating an IBM Java installation.
Determine exact SR and FP level

For IBM Java 5.0, 6, 6.0.1, and 7, identify the Service Release (SR) and Fix Pack (FP) levels from the version output. For example, SR16-FP3 indicates Service Release 16, Fix Pack 3.

Affected if The SR/FP level is lower than: SR16-FP3 for Java 5.0, SR14 for Java 6, SR6 for Java 6.0.1, or SR5 for Java 7.
Check Java 1.4.2 installations

For legacy systems still running Java 1.4.2, verify the exact SR and FP level. IBM Java 1.4.2 displays as version 1.4.2.

Affected if The version shows 1.4.2 SR13-FP17 or earlier.

Your environment is affected if IBM Java is installed and the version (including SR and FP levels) is lower than the fixed versions: 1.4.2 SR13-FP18, 5.0 SR16-FP3, 6 SR14, 6.0.1 SR6, or 7 SR5.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade affected IBM Java installations to the specified fixed versions (1.4.2 SR13-FP18, 5.0 SR16-FP3, 6 SR14, 6.0.1 SR6, or 7 SR5 or later) or migrate to supported Java versions.

Fix this in Java Scoped from the published advisory

Consultation12.0 h
Implementation24.0 h
Testing24.0 h
Review / QA8.0 h

68.0 hours of engineering $11,760

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2013-3012 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2013-3012?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 4.4%

Affects: Java

Remediation

A high-priority fix

Fix this in Java 68 hrs · High

Typical engagement from $11,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2013-3012 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References