dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 18 Apr 2022. Known ransomware use
JreApplication · Oracle

CVE-2013-2465

CRITICAL · 9.8 CVSS v3.1 Published 2013-06-18
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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 Runtime Environment (JRE) component in Oracle Java SE 7 Update 21 and earlier, 6 Update 45 and earlier, and 5.0 Update 45 and earlier, and OpenJDK 7, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D. NOTE: the previous information is from the June 2013 CPU. Oracle has not commented on claims from another vendor that this issue allows remote attackers to bypass the Java sandbox via vectors related to "Incorrect image channel verification" in 2D.

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

Heap overflow vulnerability in Java's 2D image processing component allows remote attackers to bypass the Java sandbox and execute arbitrary code by crafting malicious images with incorrect channel verification, leading to complete system compromise.

MitigationUpgrade Java SE to versions beyond 7u21, 6u45, and 5u45. If immediate patching is not feasible, disable Java browser plugins and restrict Java Web Start execution to untrusted content.

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
JreApplication
Affected:= 1.7.0= 1.6.0= 1.5.0
JreApplication
Affected:= 1.6.0= 1.5.0
Linux Enterprise DesktopOperating system
Affected:= 10
Linux Enterprise JavaOperating system
Affected:= 10= 11
Linux Enterprise ServerOperating system
Affected:= 10= 11
Linux Enterprise Software Development KitOperating system
Affected:= 11

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Determine installed Java version
    Run 'java -version' or 'java -fullversion' from command line to retrieve the exact Java version installed
    Affected if The version shown is Java 7u21 or earlier, Java 6u45 or earlier, Java 5u45 or earlier, or OpenJDK 7 without updates
  2. Check Java vendor and update level
    Run 'java -version 2>&1' and examine the full version string including the update number (for example, 1.7.0_21 or 1.6.0_45)
    Affected if The version string indicates an update number at or below the affected thresholds for the respective major version
  3. Verify Java browser plugin presence
    Check browser plugin directories for Java plugin files (on Windows: check Plugin directory in browser installation; on Linux: check ~/.mozilla/plugins or /usr/lib/mozilla/plugins)
    Affected if Java browser plugin is installed and enabled, as the vulnerability can be exploited through malicious applets loaded via browser
  4. Confirm Java Web Start availability
    Look for javaws executable on the system by running 'which javaws' or checking for JNLP file associations
    Affected if Java Web Start is installed and accessible, as the vulnerability can also be triggered through Java Web Start applications

A system is affected if it runs any Java version within the vulnerable ranges (Java 7u21 and earlier, 6u45 and earlier, 5u45 and earlier, or OpenJDK 7) and has the Java browser plugin or Java Web Start enabled, as the flaw in the 2D image processing component can then be exploited to bypass the Java sandbox.

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
Patch available Apply the vendor patch
Vendor patch hg.openjdk.java.net →
Interim mitigation

Upgrade Java SE to versions beyond 7u21, 6u45, and 5u45. If immediate patching is not feasible, disable Java browser plugins and restrict Java Web Start execution to untrusted content.

Recommended fix High confidence

Oracle Java SE 7 Update 25 or later / OpenJDK 7u40 or later (or OpenJDK 8)

  1. 1. Identify current Java version by running 'java -version' in terminal
  2. 2. For Oracle Java: download and install Java SE 7 Update 25 or later from oracle.com/java/technologies/downloads/
  3. 3. For OpenJDK: install a patched version from your Linux distribution's package manager (e.g., 'zypper update' for SUSE, or install openjdk-7u40 or later from standard repos)
  4. 4. Update JAVA_HOME environment variable to point to the new Java installation directory
  5. 5. Verify the upgrade was successful by running 'java -version' and confirming the new version number
  6. 6. Test critical applications to ensure they function correctly with the upgraded Java
Caveat Java version upgrades may cause compatibility issues with legacy applications; test thoroughly before production deployment

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

Fix this in Jre Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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