CriticalCVE-2012-1723

    Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution Vulnerability (CVE-2012-1723)

    Published Last modified In CISA KEV since Sources: CVE.org

    What is affected, what to do

    This vulnerability allows remote attackers to execute arbitrary code via the Java Runtime Environment (JRE) in Oracle Java SE by exploiting unspecified vectors related to Hotspot. It affects Oracle Java SE versions 7 Update 4 and earlier, 6 Update 32 and earlier, 5 Update 35 and earlier, and 1.4.2_37 and earlier. The vulnerability impacts confidentiality, integrity, and availability and is actively exploited in ransomware campaigns. Immediate patching to the latest version is critical to mitigate this risk.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update Red Hat IcedTea6 to version 1.10.8, Red Hat IcedTea6 to version 1.11.3. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Oracle JDK lte *..1.4.2_37
    • Oracle JDK eq 1.5.0..1.5.0
    • Oracle JDK eq 1.6.0..1.6.0
    • Oracle JDK eq 1.7.0..1.7.0
    • Oracle JRE lte *..1.4.2_37
    • Oracle JRE eq 1.5.0..1.5.0
    • Oracle JRE eq 1.6.0..1.6.0
    • Oracle JRE eq 1.7.0..1.7.0
    • Red Hat IcedTea6 lt *..1.10.8
    • Red Hat IcedTea6 lt 1.11.0..1.11.3
    • Redhat Enterprise Linux Desktop eq 5.0..5.0
    • Redhat Enterprise Linux Desktop eq 6.0..6.0
    • Red Hat Enterprise Linux Extended Update Support (EUS) eq 6.2..6.2
    • Redhat Enterprise Linux Server eq 5.0..5.0
    • Redhat Enterprise Linux Server eq 6.0..6.0
    • Redhat Enterprise Linux Server Advanced mission critical Update Support (AUS) eq 6.2..6.2
    • Redhat Enterprise Linux Workstation eq 5.0..5.0
    • Redhat Enterprise Linux Workstation eq 6.0..6.0
    Fixed in
    • Red Hat IcedTea6 1.10.8
    • Red Hat IcedTea6 1.11.3

    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: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org

    93.6 %

    EPSS score

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

    Source: FIRST EPSS, percentile 99.84

    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.74 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
    93.6 %
    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.84
    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
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 3 March 2022
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-284

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw gives an unauthenticated, network-delivered full escape from the Java sandbox and was a staple of exploit kits in drive-by campaigns for years; CISA flags known use in ransomware campaigns, and its exploitation likelihood ranks among the very highest of all tracked CVEs. Typical targets are workstations with an outdated JRE and an active browser plug-in — today mostly forgotten legacy systems, line-of-business clients, kiosks and OT operator stations. Organisations without legacy Java face little residual risk, but any affected JRE with internet reachability should be treated as critical and eliminated within 24 hours, since working exploits are freely available.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory every Java runtime via EDR/software management (SCCM, Intune, osquery): collect java.exe/javaw.exe versions and the registry keys under HKLM\SOFTWARE\JavaSoft\Java Runtime Environment (including WOW6432Node). Affected: Java SE 7 Update 4 and earlier, 6 Update 32 and earlier, 5.0 Update 35 and earlier, 1.4.2_37 and earlier.
      • Remove or replace affected JREs: move Java 7/6 to a currently vendor-supported Java SE release — patch available from the vendor, look up the exact version in the Oracle Critical Patch Update advisory. Java 5 and 1.4.2 have long been out of support: uninstall outright or relocate to isolated legacy zones.
      • Disable Java in the browser now: turn off the Java plug-in/ActiveX control in Internet Explorer and any legacy browsers via GPO; on newer JREs set deployment.webjava.enabled=false in the system-wide deployment.properties (locked with .locked). This is a HotSpot sandbox escape — the primary vector is malicious applets delivered via drive-by browsing.
      • Isolate high-risk hosts: clients that combine an affected JRE with a browser running the Java plug-in go into a quarantine VLAN or proxy-only access without direct internet until remediated.
      • Hunt for compromise on every host with an affected JRE: EDR query for child processes of java.exe/javaw.exe over the last 90 days (see detection rules). On a hit, isolate the host and reset credentials of users who logged on there.

    2. Runbook step 2

      Mitigation layers

      • Network/proxy: block downloads of .jar, .class and JNLP files (MIME application/java-archive, application/x-java-applet, application/x-java-jnlp-file) at the web proxy for all users; allowlist only documented business applications.
      • IPS/WAF: enable exploit-kit and Java applet exploit signatures in Suricata/Snort (ET "exploit_kit" category plus Java rules) in blocking mode; consider TLS inspection for "uncategorized/newly registered" domain categories.
      • Endpoint hardening: use AppLocker/WDAC to deny execution of java.exe, javaw.exe and jp2launcher.exe from legacy JRE paths (C:\Program Files*\Java\jre6\, jre7\ at Update 4 or lower, jre1.5*, j2re1.4*); add ASR rules blocking executable content from email/webmail and process creation from PSExec/WMI.
      • Legacy business apps: if an application genuinely requires an old JRE, run it only inside an isolated VM/terminal server without internet access, with a Deployment Rule Set or Exception Site List pinned to the single internal URL.
      • IAM/least privilege: run users without local admin rights — after a sandbox escape the payload runs in user context, and denying admin rights substantially hinders persistence and lateral movement.

    3. Runbook step 3

      Detection rules

      • Sysmon EID 1 / Windows 4688 — suspicious process ancestry: ParentImage ends in \java.exe, \javaw.exe or \jp2launcher.exe and Image is cmd.exe, powershell.exe, wscript.exe, cscript.exe, rundll32.exe, regsvr32.exe or mshta.exe. KQL: DeviceProcessEvents | where InitiatingProcessFileName in~ ("java.exe","javaw.exe","jp2launcher.exe") and FileName in~ ("cmd.exe","powershell.exe","rundll32.exe","regsvr32.exe","mshta.exe","wscript.exe")
      • Sysmon EID 11 — file creation: a Java process writes .exe, .dll or .scr into %TEMP%, %APPDATA% or %LOCALAPPDATA%; a subsequent EID 1 executing that path is a strong exploitation indicator.
      • Proxy/Zeek telemetry: Zeek files.log with mime_type == "application/java-archive" or http.log .jar downloads from rare external domains, closely followed by a PE download (application/x-dosexec) to the same client. SPL: index=proxy (uri="*.jar" OR content_type="application/java-archive") | stats count by src_ip, dest_host | where count<3
      • Network connections (Sysmon EID 3): java.exe/javaw.exe on workstations connecting outbound to non-standard ports or directly to raw IPs without prior DNS resolution.
      • Inventory rule: daily SIEM correlation of software inventory against affected JRE versions as a compliance alert (asset-drift detection).

    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 4 and earlier, 6 update 32 and earlier, 5 update 35 and earlier, and 1.4.2_37 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Hotspot.

    Source: CISA KEV Catalog, cvelistv5, NVD (NIST), 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
    oraclejdk
    • 1.5.0
    • 1.6.0
    • 1.7.0
    • ≤ 1.4.2_37
    • —
    • —
    • —
    • —
    oraclejre
    • 1.5.0
    • 1.6.0
    • 1.7.0
    • ≤ 1.4.2_37
    • —
    • —
    • —
    • —
    redhaticedtea6
    • < 1.10.8
    • 1.11.0 – < 1.11.3
    • 1.10.8
    • 1.11.3

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxredhatenterprise_linux_desktop5.0
    Linuxredhatenterprise_linux_desktop6.0
    Linuxredhatenterprise_linux_eus6.2
    Linuxredhatenterprise_linux_server5.0
    Linuxredhatenterprise_linux_server6.0
    Linuxredhatenterprise_linux_server_aus6.2
    Linuxredhatenterprise_linux_workstation5.0
    Linuxredhatenterprise_linux_workstation6.0

    Weakness classes (CWE)

    • CWE-284Improper Access Control

      Pillar

      The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

      Entry at MITRE CWE-284

    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

    • security.gentoo.orgGLSA-201406-32Vendor advisory, x_refsource_GENTOO
    • rhn.redhat.comRHSA-2012:0734Vendor advisory, x_refsource_REDHAT
    • oracle.comtechnetwork/topics/security/javacpujun2012-1515912.htmlx_refsource_CONFIRM
    • mail.openjdk.java.net[OpenJDK] 20120612 IcedTea6 1.10.8 & 1.11.3 ReleasedMailing list, x_refsource_MLIST
    • marc.infoSSRT100919Vendor advisory, x_refsource_HP
    • oval.cisecurity.orgoval:org.mitre.oval:def:16259Vulnerability database, signature, x_refsource_OVAL
    • securityfocus.com53960Vulnerability database, x_refsource_BID
    • mandriva.comMDVSA-2012:095Vendor advisory, x_refsource_MANDRIVA
    • ibm.comsupport/docview.wss?uid=swg21615246x_refsource_CONFIRM
    • secunia.com51080Third-party advisory, x_refsource_SECUNIA
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2012-1723government-resource

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentchanged
      {"id":"CVE-2012-1723","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-05T20:52:47.890615Z"}
      {"id":"CVE-2012-1723","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2022-03-03T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentchanged
      {"id":"CVE-2012-1723","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"rapid"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2022-03-03T00:00:00+00:00"}
      {"id":"CVE-2012-1723","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-05T20:52:47.890615Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    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-2012-1723
    <a href="https://intel.neosec.eu/en/cve/CVE-2012-1723"><img src="https://intel.neosec.eu/badge/cve/CVE-2012-1723.svg?lang=en" alt="CVE-2012-1723 – NEOSEC Intel" height="20"></a>