dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-0457

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, SE 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 Libraries.

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

CVE-2014-0457 is a critical severity vulnerability in Oracle Java SE/JRockit that was patched in the January 2014 Critical Patch Update. While officially 'unspecified,' this and related CVEs from that period were historically identified as Java sandbox bypass vulnerabilities allowing remote code execution by escaping Java's security manager restrictions. The complete CIA impact (Confidentiality, Integrity, Availability) indicates arbitrary code execution with full privileges.

MitigationApply the January 2014 Critical Patch Update for affected Java versions, or upgrade to a later supported Java version (Java 8u60+, Java 11+) which is not affected by this legacy vulnerability.

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. Identify installed Oracle Java JDK/JRE version
    Run 'java -version' or 'java -fullversion' from command line to retrieve the installed Java version string. On Linux systems, also check /usr/lib/jvm/ or /usr/java/ directories for installed JDK/JRE packages.
    Affected if The version reported is 1.5.0, 1.6.0, 1.7.0, or 1.8.0 (any update number within these major versions). These versions were patched in January 2014 and remain vulnerable unless the specific CPU patch was applied.
  2. Check for Oracle JRockit installation
    Locate JRockit installation directory (commonly /oracle/middleware/jrockit* or /usr/lib/jvm/jrockit*) and run 'java -version' from that directory. JRockit versions display as r27.x or r28.x.
    Affected if Installed JRockit version is r27.8.1 or r28.3.1, which are the specific affected versions listed.
  3. Detect Java network exposure
    Run 'netstat -anp | grep java' or 'ss -tlnp | grep java' to list Java processes listening on network ports. Also check 'ps aux | grep java' for running Java processes.
    Affected if Java is running as a network service (listener on ports 8080, 443, 7001, or similar) on untrusted networks without the January 2014 CPU patch applied.
  4. Check IBM Forms Viewer installation
    Locate IBM Forms installation (common paths: /opt/IBM/Forms or C:\Program Files\IBM\Forms). Check version via installer properties or version.info file in the installation directory.
    Affected if IBM Forms Viewer version is 4.0.0 through 4.0.0.2, or 8.0.0 through 8.0.1.0.
  5. Verify OS-packaged Java versions on Debian/Ubuntu
    On Debian/Ubuntu systems, run 'dpkg -l | grep -i java' or 'apt list --installed | grep -i jdk' to list Java packages installed via system package manager.
    Affected if Installed Java packages originate from Ubuntu 10.04, 12.04, 12.10, 13.10, 14.04 or Debian 6.0, 7.0, 8.0 repositories with the vulnerable JDK/JRE versions.

The environment is affected if any Oracle Java JDK/JRE version 1.5.0, 1.6.0, 1.7.0, or 1.8.0, Oracle JRockit r27.8.1 or r28.3.1, or IBM Forms Viewer 4.0.0-4.0.0.2/8.0.0-8.0.1.0 is installed and running without the January 2014 Critical Patch Update 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.

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 the January 2014 Critical Patch Update for affected Java versions, or upgrade to a later supported Java version (Java 8u60+, Java 11+) which is not affected by this legacy vulnerability.

Recommended fix High confidence

Upgrade to Java SE 5.0u61 / 6u71 / 7u51 / 8u31 or later (or latest available Oracle CPU patch); JRockit to latest R27/R28 patch; Junos Space to >= 15.1; Forms Viewer to >= 4.0.0.3 or >= 8.0.1.1

  1. Check current Java/JDK version: java -version or javac -version
  2. For Ubuntu/Debian: Run 'sudo apt-get update && sudo apt-get upgrade' or 'sudo apt-get install openjdk-7-jdk' or openjdk-8-jdk to get latest security patches
  3. For Oracle JDK: Download and install the fixed version from Oracle's Critical Patch Updates (Java 5.0u61, Java 6u71, Java 7u51, Java 8u31 or later)
  4. For JRockit: Upgrade to the latest JRockit R27.8.x or R28.3.x patch set from Oracle
  5. For Junos Space: Upgrade to version 15.1 or later as specified in the advisory
  6. For Forms Viewer: Upgrade to 4.0.0.3 or 8.0.1.1 or later
  7. Verify the upgrade was successful by checking: java -version and ensuring the version matches the fixed release
Caveat Major version upgrades (e.g., Java 6 to Java 8) may introduce API incompatibilities; test thoroughly in non-production first. End-of-life Java versions (5, 6) may require moving to newer major releases.

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

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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