dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-0455

HIGH · 9.3 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 7u51 and 8, and Java SE Embedded 7u51, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries, a different vulnerability than CVE-2014-0432 and CVE-2014-2402.

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 is a critical-severity vulnerability in Oracle Java SE (versions 7u51 and 8) and Java SE Embedded 7u51 affecting the Libraries component. With a CVSS score of 9.3, it allows remote unauthenticated attackers to achieve complete compromise of confidentiality, integrity, and availability, likely through a library-level exploit that bypasses Java's security sandbox.

MitigationApply Oracle's January 2014 Critical Patch Update (CPU) or later to obtain the fixed Java versions, and ensure all affected Java installations across the environment are identified and updated.

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:= 12.10= 13.10= 14.04
JdkApplication
Affected:= 1.7.0= 1.8.0
JreApplication
Affected:= 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
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 installed Java JDK version
    Run 'java -version' or 'javac -version' from command line and note the reported version string
    Affected if The version starts with 1.7.0 or 1.8.0 (any subversion) and the vendor is Oracle
  2. Identify installed Java JRE version
    Run 'java -version' and check the JRE vendor and version, or inspect the JRE directory path for version markers
    Affected if The JRE version is 1.7.0.x or 1.8.0.x from Oracle
  3. Check Ubuntu Linux version
    Run 'lsb_release -a' or 'cat /etc/lsb-release' on Linux systems
    Affected if The distribution is Ubuntu 12.10, 13.10, or 14.04 and Oracle Java is installed
  4. Detect IBM Forms Viewer installation
    Search for IBM Forms Viewer installation directories or check installed packages, then retrieve version information from the application
    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 Java security sandbox configuration
    Inspect Java Control Panel security settings or check java.policy files in the JRE/lib/security directory
    Affected if The vulnerability allows sandbox bypass at the library level, so any unpatched Java installation with the security manager enabled is potentially affected

Your environment is affected if Oracle Java JDK or JRE version 1.7.0.x or 1.8.0.x is installed, or if IBM Forms Viewer versions 4.0.0-4.0.0.2 or 8.0.0-8.0.1.0 are present, or if running Ubuntu 12.10/13.10/14.04 with Oracle Java.

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 or later
Fixed in 4.0.0.38.0.1.1
Interim mitigation

Apply Oracle's January 2014 Critical Patch Update (CPU) or later to obtain the fixed Java versions, and ensure all affected Java installations across the environment are identified and updated.

Recommended fix High confidence

Java 7u60+/Java 8u5+ or later stable release (preferably Java 11 LTS or newer for long-term support)

  1. 1. Identify all systems running affected Java versions (JDK/JRE 1.7.0, 1.8.0)
  2. 2. Download and install a patched version of Java SE from Oracle's official website or your distribution's package repository
  3. 3. Ensure Java is updated to a version later than 7u51/8u (for example, Java 7u60 or later, or Java 8u5 or later)
  4. 4. Verify the installed Java version using 'java -version' command
  5. 5. Update any PATH environment variables to point to the new Java installation
  6. 6. Restart any running applications or services that use Java
  7. 7. Test critical applications to ensure compatibility with the new Java version
Caveat Upgrading Java versions may introduce breaking changes for applications using deprecated APIs or specific Java 8 features; thorough testing is recommended

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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