CriticalCVE-2013-2465

    Oracle Java SE Unspecified Vulnerability (CVE-2013-2465)

    Published In CISA KEV since Sources: CVE.org

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Oracle JRE eq 1.7.0..1.7.0
    • Oracle JRE eq 1.6.0..1.6.0
    • Sun JRE 1.4.2 02 eq 1.6.0..1.6.0
    • Oracle JRE eq 1.5.0..1.5.0
    • Sun JRE 1.4.2 02 eq 1.5.0..1.5.0
    • SUSE Linux Enterprise Desktop eq 10..10
    • SUSE Linux Enterprise Java eq 10..10
    • SUSE Linux Enterprise Java eq 11..11
    • SUSE Linux Enterprise Server eq 10..10
    • SUSE Linux Enterprise Server eq 11..11
    • SUSE Linux Enterprise Software Development Kit (SDK) eq 11..11

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org

    98.8 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.93

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    253.89 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    98.8 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.93
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw allows a Java sandbox escape via crafted image data in the 2D component and was heavily weaponised in exploit kits for drive-by attacks; it is network-reachable without authentication, requires only a visit to a malicious page, and sits among the CVEs most likely to be exploited. CISA flags it as used in ransomware campaigns, typically as an initial-access vector on workstations. For most organisations the real exposure is confined to leftovers — legacy line-of-business apps, OT/HMI and operator PCs, forgotten old JREs — but where it exists it is critical: treat any vulnerable version with an active browser plug-in as fix-now, and server-side JREs without a browser context as lower but still high priority.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Query all endpoints and servers for installed JRE/JDK versions (asset inventory, EDR, wmic product where "name like 'Java%'" get name,version). Affected: Oracle Java SE 7 Update 21 and earlier, 6 Update 45 and earlier, 5.0 Update 45 and earlier, and OpenJDK 7.
      • Patch: The fix shipped in Oracle's June 2013 Critical Patch Update (Java 7 Update 25). Do not stop there — move straight to a currently supported Java release; check the Oracle advisory/support roadmap for the exact version. For OpenJDK 7, update distribution packages or migrate to a supported LTS build.
      • Remove legacy runtimes: Java 5 and 6 receive no public updates. Uninstall all side-by-side older JREs; historic Java installers routinely left previous versions behind.
      • Disable the browser plug-in: The primary vector is malicious applets delivered via drive-by download. Disable the Java browser plug-in via GPO/MDM now (Java Control Panel "Enable Java content in the browser" off, or deployment.webjava.enabled=false in deployment config).
      • Compromise assessment: On hosts that ran a vulnerable version with the plug-in enabled, hunt recent EDR telemetry for Java child processes and dropped executables (see detection rules). On a hit, isolate the host and reset the logged-on user's credentials.

    2. Runbook step 2

      Mitigation layers

      • Network/proxy: Block .jar, .jnlp and .class downloads from the internet at the web proxy, or allow them only for an allowlist of business-required domains. Additionally block and log requests with User-Agent Java/1.5*, Java/1.6*, and Java/1.7.0_0* through Java/1.7.0_21.
      • IPS/web filtering: Run signatures for known exploit-kit landing pages and Java applet exploits (Suricata/ET "EXPLOIT_KIT" and Java exploit categories) in blocking mode; block the "newly registered domains" category.
      • Endpoint hardening: Set Java security level to "Very High" via deployment.properties and use Deployment Rule Sets (DeploymentRuleSet.jar) to permit only signed, internally approved applets. Block execution from %TEMP%/%APPDATA% with AppLocker or WDAC.
      • Application isolation: Business apps that genuinely require a legacy JRE belong in isolated VDI or terminal-server environments with no internet access and no general browsing.
      • IAM/least privilege: Run end users without local admin rights to hinder persistence and privilege escalation after a successful sandbox escape.

    3. Runbook step 3

      Detection rules

      • EDR process ancestry (Sysmon EID 1 / Windows EID 4688): java.exe or javaw.exe spawning cmd.exe, powershell.exe, wscript.exe, rundll32.exe, regsvr32.exe or unknown binaries. KQL: DeviceProcessEvents | where InitiatingProcessFileName in~ ("java.exe","javaw.exe") and FileName in~ ("cmd.exe","powershell.exe","rundll32.exe","regsvr32.exe","wscript.exe")
      • File system (Sysmon EID 11): A Java process writing .exe/.dll files into %TEMP%, %APPDATA% or %LOCALAPPDATA% — the classic payload drop after applet execution.
      • Proxy/web logs: Requests with User-Agent Java/1.7.0_21 or older, especially .jar fetches immediately after visiting an external page with an unfamiliar referer. SPL: index=proxy http_user_agent="Java/1.*" (uri="*.jar" OR uri="*.jnlp") | stats count by src_ip, dest_host, http_user_agent
      • Network telemetry (Zeek/Suricata): http.log/files.log entries with MIME type application/java-archive from rare domains, followed by outbound connections (Sysmon EID 3) from the Java process or a freshly spawned child to external IPs.
      • Standing inventory check: Weekly query for hosts with Java ≤ 7u21 or Java 5/6 and an enabled browser plug-in, raised as a high-risk finding in vulnerability management.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    oraclejre
    • 1.5.0
    • 1.6.0
    • 1.7.0
    • —
    • —
    • —
    sunjre
    • 1.6.0
    • 1.5.0
    • —
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxsuselinux_enterprise_desktop10
    Linuxsuselinux_enterprise_java10
    Linuxsuselinux_enterprise_java11
    Linuxsuselinux_enterprise_server10
    Linuxsuselinux_enterprise_server11
    Linuxsuselinux_enterprise_software_development_kit11

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • rhn.redhat.comRHSA-2013:1060Vendor advisory, x_refsource_REDHAT, Third-party advisory
    • marc.infoHPSBUX02908Vendor advisory, x_refsource_HP, Mailing list, Third-party advisory
    • access.redhat.comRHSA-2014:0414Vendor advisory, x_refsource_REDHAT, Third-party advisory
    • security.gentoo.orgGLSA-201406-32Vendor advisory, x_refsource_GENTOO, Third-party advisory
    • securityfocus.com60657Vulnerability database, x_refsource_BID, Broken link, Third-party advisory, Vulnerability database
    • oracle.comtechnetwork/topics/security/javacpujun2013-1899847.htmlx_refsource_CONFIRM, Vendor advisory
    • lists.opensuse.orgSUSE-SU-2013:1264Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • lists.opensuse.orgSUSE-SU-2013:1257Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • marc.infoHPSBUX02907Vendor advisory, x_refsource_HP, Mailing list, Third-party advisory
    • lists.opensuse.orgSUSE-SU-2013:1256Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • secunia.com54154Third-party advisory, x_refsource_SECUNIA, Not applicable
    • rhn.redhat.comRHSA-2013:1455Vendor advisory, x_refsource_REDHAT, Third-party advisory
    • h20000.www2.hp.comSSRT101305Vendor advisory, x_refsource_HP, Broken link
    • oval.cisecurity.orgoval:org.mitre.oval:def:19455Vulnerability database, signature, x_refsource_OVAL, Broken link
    • oval.cisecurity.orgoval:org.mitre.oval:def:19703Vulnerability database, signature, x_refsource_OVAL, Broken link
    • hg.openjdk.java.netjdk7u/jdk7u-dev/jdk/rev/2a9c79db0040x_refsource_MISC, Patch
    • oval.cisecurity.orgoval:org.mitre.oval:def:19074Vulnerability database, signature, x_refsource_OVAL, Broken link
    • lists.opensuse.orgSUSE-SU-2013:1263Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • rhn.redhat.comRHSA-2013:1059Vendor advisory, x_refsource_REDHAT, Third-party advisory
    • lists.opensuse.orgSUSE-SU-2013:1293Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2013-2465
    <a href="https://intel.neosec.eu/en/cve/CVE-2013-2465"><img src="https://intel.neosec.eu/badge/cve/CVE-2013-2465.svg?lang=en" alt="CVE-2013-2465 – NEOSEC Intel" height="20"></a>