dbcve.org
Debian LinuxOperating system · Debian

CVE-2014-2490

HIGH · 9.3 CVSS v2.0 Published 2014-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 the Java SE component in Oracle Java SE 7u60 and SE 8u5 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Hotspot.

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 vulnerability in the Java Hotspot just-in-time (JIT) compiler component of Java SE versions 7u60 and 8u5 allows remote attackers to execute arbitrary code via unknown vectors, achieving full compromise of confidentiality, integrity, and availability.

MitigationApply Oracle Critical Patch Update for July 2014 (CPU) or later, which includes patches for CVE-2014-2490, upgrading Java to versions beyond 7u60 and 8u5.

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
Debian LinuxOperating system
Affected:= 7.0
Hp UxOperating system
Affected:= b.11.23= b.11.31
JdkApplication
Affected:= 1.7.0= 1.8.0
JreApplication
Affected:= 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
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. Check if Java is installed
    Run 'java -version' or 'which java' on the command line to determine if Java is present on the system
    Affected if Java is not installed on the system - the vulnerability does not apply
  2. Identify the exact Java version
    Run 'java -version 2>&1' to obtain the full version string (for Oracle JDK/JRE look for '1.7.0_xx' or '1.8.0_xx' in the output)
    Affected if The output shows version 1.7.0 or 1.8.0 (any update number) - this indicates a potentially affected version
  3. Confirm the specific update version
    Run 'java -fullversion 2>&1' or check the JRE/JDK installation directory for the release version file
    Affected if Version is exactly 1.7.0_60 or earlier for the 1.7.x line, or exactly 1.8.0_5 or earlier for the 1.8.x line - these are the known vulnerable versions per the CVE summary

The system is affected if Oracle Java JDK or JRE versions 1.7.0 (specifically up to and including 7u60) or 1.8.0 (specifically up to and including 8u5) are installed, as the vulnerability exists in the Java Hotspot JIT compiler component of these versions.

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

Apply Oracle Critical Patch Update for July 2014 (CPU) or later, which includes patches for CVE-2014-2490, upgrading Java to versions beyond 7u60 and 8u5.

Recommended fix High confidence

Java 8u172 (or later 8.x) / Java 7u80

  1. 1. Identify the current Java installation: java -version
  2. 2. For Oracle JDK/JRE: Download and install Java 8u172 (or later 8.x) or Java 7u80 from oracle.com/java/technologies/downloads/
  3. 3. Update JAVA_HOME environment variable to point to the new Java installation path
  4. 4. Update any PATH references to point to the new Java binaries
  5. 5. Verify the upgrade: java -version should show the new version number
  6. 6. For Debian: Run 'apt-get update && apt-get upgrade' to apply Debian Java security updates
  7. 7. For HP-UX: Download and apply HP patch PHSS_xyz from support.hp.com for your HP-UX version
Caveat Java 7 reached end-of-life; consider migrating to Java 8+ for continued security updates. Some legacy applications may have compatibility issues with newer Java versions.

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

Fix this in Debian 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-2490 — 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-2490 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