dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-0429

HIGH · 10.0 CVSS v2.0 Published 2014-04-16
Fix available
A fix is available. Upgrade to 4.0.0.3 / 8.0.1.1 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
Unspecified vulnerability in Oracle Java SE 5.0u61, 6u71, 7u51, and 8; JRockit R27.8.1 and R28.3.1; and Java SE Embedded 7u51 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.

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

Critical remote code execution vulnerability in the Java 2D graphics subsystem (CVE-2014-0429) affecting Java SE 5.0u61 through 8, JRockit R27.8.1/R28.3.1, and Java SE Embedded 7u51. The unspecified flaw in 2D image processing allows remote attackers to achieve full compromise of confidentiality, integrity, and availability via maliciously crafted visual content or applets.

MitigationApply Oracle Critical Patch Update February 2014 or later to upgrade affected Java installations to patched versions. Remove or disable older vulnerable Java versions from endpoints and servers where possible.

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
Ubuntu LinuxOperating system
Affected:= 10.04= 12.04= 12.10= 13.10= 14.04
Debian LinuxOperating system
Affected:= 6.0= 7.0= 8.0
JrockitApplication
Affected:= r27.8.1= r28.3.1
Junos SpaceApplication
Affected:< 15.1
JdkApplication
Affected:= 1.5.0= 1.6.0= 1.7.0= 1.8.0
JreApplication
Affected:= 1.5.0= 1.6.0= 1.7.0= 1.8.0
Forms ViewerApplication
Affected:>= 4.0.0, < 4.0.0.3>= 8.0.0, < 8.0.1.1

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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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. Check Java/JRE/JDK version installed
    Run 'java -version' or 'javac -version' from command line to see the installed Java version
    Affected if Version is 1.5.0u61 through 1.8.0 (any update within these release families), or specifically r27.8.1 or r28.3.1 for JRockit, or 7u51 for Java SE Embedded
  2. Check for multiple Java installations
    On Linux/Unix check /usr/lib/jvm/ or /opt/java/ directories; on Windows check Program Files/Java for multiple version folders
    Affected if Any folder contains a vulnerable Java version as defined above
  3. Verify IBM Forms Viewer version if installed
    Check product version through its About dialog or look for version files in the installation directory
    Affected if Version is 4.0.0.x where x < 3, or 8.0.0.x where x < 1 (8.0.1.0 and below)
  4. Confirm Java plugin is enabled in browsers
    Check browser plugin settings (about:addons in Firefox, Chrome plugins page) for Java Applet plugin status
    Affected if Java browser plugin is enabled and vulnerable Java version is installed, allowing applets to execute

Your environment is affected if any installed Java SE, JRockit, Java SE Embedded, or IBM Forms Viewer version falls within the affected version ranges and the Java 2D subsystem (typically via applets or visual content processing) is in use.

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
Upgrade available Upgrade to 4.0.0.3 / 8.0.1.1 / 15.1 or later
Fixed in 4.0.0.38.0.1.115.1
Interim mitigation

Apply Oracle Critical Patch Update February 2014 or later to upgrade affected Java installations to patched versions. Remove or disable older vulnerable Java versions from endpoints and servers where possible.

Recommended fix High confidence

Oracle Java SE 5.0u65+, 6u75+, 7u55+, 8u5+ or OpenJDK equivalents from distribution vendors

  1. Identify the currently installed Java version by running 'java -version' or checking the package manager
  2. For Ubuntu/Debian: Run 'apt-get update' and 'apt-get install openjdk-<version>-jdk' or 'openjdk-<version>-jre' to upgrade to a patched version
  3. For Oracle JRockit: Download and install the latest JRockit R28.3.4 or later patch from Oracle
  4. For Junos Space: Upgrade to Junos Space version 15.1 or later which contains the patched Java
  5. For Forms Viewer: Upgrade to version 4.0.0.3 or 8.0.1.1 or later respectively
  6. After upgrading, verify the new Java version with 'java -version' to confirm the patch was applied
  7. Restart any services or applications using the old Java version
Caveat Upgrading Java versions may require recompilation of Java applications if they depend on removed APIs or behavior changes between major versions; test thoroughly before production deployment

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

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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