Security readout for executives and security teams
Plain-English summary
This critical flaw affects multiple obsolete Oracle Java Runtime Environment releases. A remote attacker could compromise sensitive data, alter systems, or disrupt services. CISA lists it as known exploited, but the supplied evidence does not establish whether exploitation remains active today.
Executive priority
Treat confirmed exposure as an immediate remediation priority because exploitation is documented and potential impact spans data theft, unauthorized modification, and service disruption. Prioritize internet-reachable and business-critical systems, while recognizing that the supplied sources do not establish current targeting.
Technical view
CVE-2012-1723 is an unspecified HotSpot-related JRE vulnerability affecting Java SE 7 update 4 and earlier, 6 update 32 and earlier, 5 update 35 and earlier, and 1.4.2_37 and earlier. The supplied CVSS 3.1 score is 9.8, indicating network reachability, low complexity, no privileges, no user interaction, and high impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is most likely where the listed legacy JRE versions remain installed, embedded in applications, or operating on reachable systems. The bundle provides no affected CPE inventory, deployment prevalence, or reliable method for determining exposure beyond version identification.
Exploitation context
CISA's Known Exploited Vulnerabilities catalog confirms that exploitation has occurred. The provided sources do not describe current campaign activity, exploitation frequency, attack vectors, public exploit availability, or specific attacker objectives. Treat confirmed legacy exposure as urgent without assuming exploitation is presently widespread.
Researcher notes
The public description leaves the vulnerability mechanism and vectors unspecified beyond a relationship to HotSpot. CWE-284 is supplied, but it is insufficient to infer the exact defect. Avoid concluding arbitrary code execution, sandbox escape, or a particular delivery method without additional authoritative evidence.
Mitigation direction
- Inventory and prioritize systems running the listed Java versions.
- Consult current Oracle guidance for supported upgrades or vendor-approved remediation.
- Replace or remove obsolete JRE installations where operationally feasible.
- Restrict network access to exposed legacy Java-dependent systems until remediated.
- Apply compensating controls when embedded Java cannot be promptly replaced.
Validation and detection
- Verify installed and application-embedded JRE versions against the affected thresholds.
- Confirm no production asset still requires the vulnerable releases.
- Rescan remediated assets and investigate conflicting version results.
- Review security telemetry for suspicious activity involving identified legacy Java systems.
- Document exceptions, compensating controls, owners, and remediation deadlines.
Public sources used
The source record changed after analysis: Material source record changed after analysis.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2012-1723 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- oval:org.mitre.oval:def:16259CVE reference, oracle · vdb-entry, signature
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2012-1723CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.