dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2014-0460

MEDIUM · 5.8 CVSS v2.0 Published 2014-04-16
Fix available
A fix is available. Upgrade to 15.1 or later.
See remediation →
67/100
Remediation priority · Elevated
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 and integrity via vectors related to JNDI.

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 remote code execution vulnerability in Oracle Java SE and JRockit affecting the JNDI (Java Naming and Directory Interface) component. The vulnerability allows remote attackers to compromise confidentiality and integrity by exploiting unspecified vectors related to JNDI lookup operations.

MitigationApply the relevant Oracle Critical Patch Update for February 2014 which addresses this vulnerability, or upgrade to a patched Java version. For legacy systems that cannot be updated, restrict network access to Java RMI/IIOP endpoints and disable JNDI remote lookup features.

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

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

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

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 product
    Run 'java -version' or 'java -showversion' to see if Java is installed and identify whether it is Oracle Java JRE/JDK or JRockit
    Affected if The output shows Oracle Java (JDK/JRE) or JRockit is installed
  2. Determine exact Java version
    Run 'java -version 2>&1' and capture the full version string (e.g., 1.7.0_51, 1.8.0_xx)
    Affected if The version matches 1.5.0, 1.6.0, 1.7.0, or 1.8.0 exactly (or is an older update within these major versions)
  3. Check JRockit specific version
    If using JRockit, run 'java -version' and check for r27.8.1 or r28.3.1
    Affected if JRockit version is r27.8.1 or r28.3.1
  4. Check Ubuntu/Debian Java package version
    On Ubuntu/Debian systems, run 'dpkg -l | grep -i java' or check the installed openjdk packages with 'apt-cache policy openjdk-*'
    Affected if The system is Ubuntu 10.04, 12.04, 12.10, 13.10, or 14.04, or Debian 6.0, 7.0, or 8.0 with Java installed from the default repositories
  5. Check Juniper Junos Space version
    Log into Junos Space and run 'show version' or check the UI for the software version
    Affected if Junos Space version is below 15.1 (any version from initial release through 14.x)
  6. Verify JNDI is in use
    Review application configurations, look for javax.naming.* imports in application code, or check for JNDI datasources in application servers (e.g., context.xml, web.xml files)
    Affected if The application uses JNDI lookup operations, particularly against remote naming services

You are affected if you have Oracle Java (JDK/JRE) versions 1.5.0, 1.6.0, 1.7.0, or 1.8.0, JRockit r27.8.1 or r28.3.1, or Juniper Junos Space below 15.1, and your application uses JNDI lookup operations against remote services.

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

Apply the relevant Oracle Critical Patch Update for February 2014 which addresses this vulnerability, or upgrade to a patched Java version. For legacy systems that cannot be updated, restrict network access to Java RMI/IIOP endpoints and disable JNDI remote lookup features.

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