dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-0454

HIGH · 7.5 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 →
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 7u51 and 8, and Java SE Embedded 7u51, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Security.

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 · low confidence

Unspecified vulnerability in Oracle Java SE 7u51 and 8, and Java SE Embedded 7u51, affecting the Security component. Allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors, indicating a serious flaw in Java's security subsystem.

MitigationUpdate Oracle Java SE to a patched version beyond 7u51/8, or apply Oracle Critical Patch Updates. For systems that cannot update immediately, consider restricting Java network access or disabling Java browser plugins.

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
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 Oracle Java JDK version
    Run 'java -version' or 'javac -version' to identify the installed JDK version
    Affected if Version shows 1.7.0 or 1.8.0 (any subversion) and is not patched beyond 7u51/8
  2. Check Oracle Java JRE version
    Run 'java -version' and check the JRE installation path with 'which java' or 'ls -la $(which java)'
    Affected if JRE version reports 1.7.0 or 1.8.0 and is not patched beyond 7u51/8
  3. Check Ubuntu distribution version
    Run 'lsb_release -a' or check '/etc/lsb-release'
    Affected if Ubuntu version is 12.10, 13.10, or 14.04 with unpatched Java packages
  4. Check IBM Forms Viewer version
    Locate IBM Forms Viewer installation and run 'java -jar formsview.jar -version' or check version file in installation directory
    Affected if Version is 4.0.0 through 4.0.0.2, or 8.0.0 through 8.0.1.0
  5. Verify Java Security component is in use
    Check for security.policy files, java.security.manager system property, or Security Manager configuration in deployment.properties
    Affected if Java Security Manager or security-related configurations are enabled, making the Security component vulnerability applicable

You are affected if you run any Oracle Java JDK/JRE version 1.7.0 or 1.8.0 (unpatched beyond 7u51/8), Ubuntu 12.10/13.10/14.04 with vulnerable Java packages, or IBM Forms Viewer 4.0.0-4.0.0.2/8.0.0-8.0.1.0.

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

Update Oracle Java SE to a patched version beyond 7u51/8, or apply Oracle Critical Patch Updates. For systems that cannot update immediately, consider restricting Java network access or disabling Java browser plugins.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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