dbcve.org
JavaApplication · Ibm

CVE-2012-4822

HIGH · 9.3 CVSS v2.0 Published 2013-01-11
Fix available
A fix is available. Upgrade to after 7.0.2.0 or later.
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
Multiple unspecified vulnerabilities in the JRE component in IBM Java 7 SR2 and earlier, Java 6.0.1 SR3 and earlier, Java 6 SR11 and earlier, Java 5 SR14 and earlier, and Java 142 SR13 FP13 and earlier; as used in IBM Rational Host On-Demand, Rational Change, Tivoli Monitoring, Smart Analytics System 5600, Tivoli Remote Control 5.1.2, WebSphere Real Time, Lotus Notes & Domino, Tivoli Storage Productivity Center, and Service Deliver Manager; and other products from other vendors such as Red Hat, allow remote attackers to execute arbitrary code via vectors related to "insecure use [of] multiple methods in the java.lang.class class."

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 · moderate confidence

This CVE involves multiple unspecified vulnerabilities in IBM Java JRE (versions 7 SR2 and earlier, 6.0.1 SR3 and earlier, 6 SR11 and earlier, 5 SR14 and earlier, and 142 SR13 FP13 and earlier) that allow remote attackers to execute arbitrary code through insecure use of methods in the java.lang.Class class. The vulnerability affects numerous IBM products including Rational Host On-Demand, Tivoli Monitoring, Lotus Notes & Domino, and WebSphere Real Time.

MitigationApply IBM Java security patches to upgrade to patched versions of the JRE, or disable Java in affected systems if patches are unavailable. Given the critical CVSS score of 9.3 and remote code execution capability, prioritize patching affected systems immediately.

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.13>= 5.0.0.0, <= 5.0.14.0>= 6.0.0.0, <= 6.0.11.0>= 7.0.0.0, <= 7.0.2.0
Lotus DominoApplication
Affected:= 8.0= 8.0.1= 8.0.2= 8.0.2.1= 8.0.2.2= 8.0.2.3= 8.0.2.4= 8.5.0= 8.5.0.1= 8.5.1= 8.5.1.1= 8.5.1.2
Lotus NotesApplication
Affected:= 8.0= 8.0.0= 8.0.1= 8.0.2= 8.0.2.0= 8.0.2.1= 8.0.2.2= 8.0.2.3= 8.0.2.4= 8.0.2.5= 8.0.2.6= 8.5
Lotus Notes SametimeApplication
Affected:= 8.0.80407= 8.0.80822= 8.5.1.20100709-1631
Lotus Notes TravelerApplication
Affected:= 8.0= 8.0.1= 8.0.1.2= 8.0.1.3= 8.5.0.0= 8.5.0.1= 8.5.0.2= 8.5.1.1= 8.5.1.2= 8.5.1.3= 8.5.2.1= 8.5.3
Rational ChangeApplication
Affected:= 4.7= 5.1= 5.2= 5.3
Rational Host On DemandApplication
Affected:= 1.6.0.12= 8.0.8.0= 9.0.8.0= 10.0.9.0= 10.0.10.0= 11.0.3.0= 11.0.4.0= 11.0.5.0= 11.0.5.1= 11.0.6.0= 11.0.6.1
Service Delivery ManagerApplication
Affected:= 7.2.1.0= 7.2.2.0

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' or check for IBM Java installations in common paths like /opt/ibm/java or the system PATH. Look for 'IBM' or 'J9' in the version output.
    Affected if IBM Java is present and the output shows IBM in the vendor string
  2. Determine IBM Java version number
    Run 'java -fullversion' or 'java -version' to obtain the exact version string. For IBM Java 5, 6, and 7, note the SR (Service Release) number. For Java 1.4.2, note the FP (Fix Pack) level.
    Affected if Version falls within: 1.4.2 to 1.4.2.13.13, 5.0.0.0 to 5.0.14.0, 6.0.0.0 to 6.0.11.0, or 7.0.0.0 to 7.0.2.0
  3. Check for vulnerable IBM products
    List installed IBM products on the system. For Lotus products, check the About or Version information in the application. For Rational Host On-Demand, check the installed version in the program's properties.
    Affected if One of these products is installed: Lotus Domino (8.0-8.5.1.2), Lotus Notes (8.0-8.5), Lotus Notes Sametime (8.0.80407, 8.0.80822, 8.5.1), Lotus Notes Traveler (8.0-8.5.3), Rational Change (4.7-5.3), Rational Host On-Demand (1.6.0.12, 8.0.8.0-11.0.6.1), or Service Delivery Manager (7.2.1.0-7.2.2.0)
  4. Verify Java is enabled in the affected application
    For Lotus Notes and Domino, check the Java debugger settings or any custom Java agents. For Rational Host On-Demand, verify if Java applets or embedded Java features are enabled.
    Affected if Java is enabled or available to remote attackers in any of the affected applications

You are affected if IBM Java is installed and its version falls within the vulnerable ranges, OR if any of the listed IBM products are installed without corresponding security patches applied.

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.

From vendor data
Upgrade available Upgrade to a release after 7.0.2.0
Interim mitigation

Apply IBM Java security patches to upgrade to patched versions of the JRE, or disable Java in affected systems if patches are unavailable. Given the critical CVSS score of 9.3 and remote code execution capability, prioritize patching affected systems immediately.

Fix this in Java Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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