dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-2412

HIGH · 7.5 CVSS v2.0 Published 2014-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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, SE 7u51, and 8, and Java SE Embedded 7u51, allows remote attackers to affect confidentiality, integrity, and availability via vectors related to AWT, a different vulnerability than CVE-2014-0451.

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

A high-severity vulnerability in Oracle Java's Abstract Window Toolkit (AWT) component allows remote attackers to fully impact confidentiality, integrity, and availability. This affects Java SE 5.0u61, 6u71, 7u51, 8 and Java SE Embedded 7u51. The vulnerability is remotely exploitable via the network.

MitigationApply the Oracle Critical Patch Update (April 2014) that addresses CVE-2014-2412, upgrading affected Java installations to patched versions. Prioritize externally-facing systems and those processing untrusted input.

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
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

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
Partial
Integrity
Partial
Availability
Partial

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

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 if Java is installed
    Run 'java -version' or 'which java' to determine if Java runtime is present on the system
    Affected if Java is not installed means the system is not affected by this specific Java vulnerability, but if Java is present, continue to version check
  2. Identify installed Java version
    Run 'java -version' (check first line for version number) and 'javac -version' if JDK is installed. Also check package manager: on Debian/Ubuntu run 'dpkg -l | grep -i java' or 'apt-cache policy openjdk-*'
    Affected if The output shows a version string starting with 1.5.0, 1.6.0, 1.7.0, or 1.8.0 indicating an affected version
  3. Confirm exact version against affected ranges
    Compare the installed version number to: Java SE 5.0u61 and below, 6u71 and below, 7u51 and below, or 8 any version. For Java SE Embedded 7u51 and below. On Linux, also check if the OS version matches Ubuntu 10.04, 12.04, 12.10, 13.10, 14.04 or Debian 6.0, 7.0, 8.0 with bundled Java
    Affected if The installed Java version falls within 1.5.0, 1.6.0, 1.7.0 (before security fix), or 1.8.0, or the OS is an affected Ubuntu/Debian version with default Java packages
  4. Verify AWT component is accessible
    Confirm the Java installation includes the AWT library by checking for awt.jar or running code that imports java.awt - the vulnerability exists in this component. Most standard Java installations include AWT by default
    Affected if Java AWT component is present in the installation, which is the default in most JDK/JRE packages

A user is affected if they have Java installed with version 1.5.0 through 1.8.0 (specifically prior to the April 2014 Critical Patch Update) on an affected Ubuntu or Debian Linux version, as the vulnerability in the AWT component can be exploited remotely.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update (April 2014) that addresses CVE-2014-2412, upgrading affected Java installations to patched versions. Prioritize externally-facing systems and those processing untrusted input.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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