JreApplication · Sun

CVE-2012-0499

HIGH · 10.0 CVSS v2.0 Published 2012-02-15

Fix available

A fix is available. Upgrade to after 2.0.2 or later.

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) component in Oracle Java SE 7 Update 2 and earlier, 6 Update 30 and earlier, 5.0 Update 33 and earlier, and 1.4.2_35 and earlier; and JavaFX 2.0.2 and earlier; allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.

Technical summary

dbcve analysis · high confidence

Critical remote code execution vulnerability in Java Runtime Environment's 2D graphics component (CVE-2012-0499) affecting Java SE 7u2 and earlier, 6u30 and earlier, 5.0u33 and earlier, and 1.4.2_35 and earlier, as well as JavaFX 2.0.2 and earlier. The unspecified flaw in the 2D rendering subsystem allows remote attackers to achieve full compromise (CIA) without authentication.

MitigationApply vendor-supplied patches by updating to Java SE 7 Update 3 or later, 6 Update 31 or later, 5.0 Update 34 or later, or 1.4.2_36 or later; alternatively, disable the Java browser plugin and remove unused Java installations until patching is feasible.

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

JreApplication

Affected:<= 1.4.2_35= 1.4.2= 1.4.2_1= 1.4.2_2= 1.4.2_3= 1.4.2_4= 1.4.2_5= 1.4.2_6= 1.4.2_7= 1.4.2_8= 1.4.2_9= 1.4.2_10

JreApplication

Affected:<= 1.6.0= 1.6.0<= 1.7.0= 1.7.0

JavafxApplication

Affected:<= 2.0.2= 1.2= 1.2.2= 1.2.3= 1.3.0= 1.3.1= 2.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: Complete
Integrity: Complete
Availability: Complete

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

Am I affected?

dbcve checks

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

Identify installed Java SE version

Run 'java -version' from command line or check the Java Control Panel (via Windows Control Panel > Java) under the General tab to see the version details

Affected if The version is Java SE 7u2 or earlier, 6u30 or earlier, 5.0u33 or earlier, or 1.4.2_35 or earlier
Check for Java browser plugin presence

Examine browser plugin directories: on Windows check C:\Program Files\Java\jreX\bin\npjp2.dll (for Java 6/7) or np*.dll in browser plugin folders; on Linux check ~/.mozilla/plugins/ or /usr/lib/mozilla/plugins/

Affected if The Java browser plugin (.dll or .so) is installed in any browser's plugin directory, making the system vulnerable to web-based exploitation of the 2D rendering flaw
Enumerate all Java installations on the system

On Windows, check registry key HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment for multiple version entries; on Unix/Linux, run 'which java' and check /usr/java/ or /opt/java/ directories for multiple installations

Affected if Any installed Java version falls within the affected ranges listed in the CVE regardless of whether it is the primary or secondary installation
Identify JavaFX installation and version

Check for JavaFX runtime in the installation directory (typically under the Java installation folder) or examine the Java Control Panel's Plugin settings for JavaFX entries

Affected if JavaFX 2.0.2 or earlier is installed, as this version contains the vulnerable 2D graphics component

A system is affected if any installed Java SE version is 7u2/6u30/5.0u33/1.4.2_35 or earlier, or JavaFX 2.0.2 or earlier, particularly if the Java browser plugin is present for remote attack vector exposure.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 2.0.2

Interim mitigation

Apply vendor-supplied patches by updating to Java SE 7 Update 3 or later, 6 Update 31 or later, 5.0 Update 34 or later, or 1.4.2_36 or later; alternatively, disable the Java browser plugin and remove unused Java installations until patching is feasible.

Recommended fix High confidence

Oracle Java SE 5.0 Update 34+, 6 Update 31+, 7 Update 3+, 1.4.2_36+ or JavaFX 2.0.3+ (Oracle no longer supports Java SE 6 and earlier for public downloads; consider migrating to a currently supported LTS version like Java SE 11, 17, or 21)

1. Identify all systems and applications running the affected Java versions (JRE 1.4.2_35 and earlier, 1.6.0 and earlier, 1.7.0 and earlier, or JavaFX 2.0.2 and earlier)
2. Download the latest Oracle Java SE release from the official Oracle website (oracle.com/java) or your distribution's package repository
3. For Java SE 5.0, upgrade to Java SE 5.0 Update 34 or later
4. For Java SE 6, upgrade to Java SE 6 Update 31 or later
5. For Java SE 7, upgrade to Java SE 7 Update 3 or later
6. For Java SE 1.4.2, upgrade to Java SE 1.4.2_36 or later
7. For JavaFX, upgrade to JavaFX 2.0.3 or later
8. Verify the new Java version by running 'java -version'

Caveat Very old Java applications written for JDK 1.4.2 or earlier may have compatibility issues with newer Java versions due to language feature changes and removed deprecated APIs; extensive testing is recommended

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

Fix this in Jre Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2012-0499 — 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-2012-0499 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2012-0499?

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 existsUpgrade to after 2.0.2 or later

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 6.3%

Affects: Jre

Remediation

A high-priority fix

Fix this in Jre 9 hrs · Low

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2012-0499 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