Cyber Resilience

CVE-2013-0431

Oracle Jre 1.7.0

CISA KEVActive ExploitationEUVD ExploitedRansomware-linked
Published
31 January 2013
Modified
21 April 2026
KEV Added
25 May 2022
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.90 99.8th percentile
Risk Priority 75 floored blend · peak EPSS

Summary

CVE-2013-0431 is a medium-severity Protection Mechanism Failure (CWE-693) vulnerability in Oracle Jre. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Abuse Elevation Control Mechanism (T1548); ranked in the top 0.2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The vulnerability is an unspecified flaw in the Java Runtime Environment component of Oracle Java SE 7 through Update 11 and OpenJDK 7. It is tracked as Issue 52 and is distinct from CVE-2013-1490. The issue resides in JMX-related code and permits bypass of the Java security sandbox.

User-assisted remote attackers can exploit the flaw over the network to circumvent sandbox restrictions and obtain limited unauthorized access to sensitive information. The CVSS 3.1 score of 5.3 reflects network attack vector, low complexity, and no required privileges or user interaction for the confidentiality impact. No mitigation details or patch guidance are provided in the available references, and no information on observed exploitation is supplied.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11, and OpenJDK 7, allows user-assisted remote attackers to bypass the Java security sandbox via unspecified vectors related to JMX, aka "Issue 52," a…

more

different vulnerability than CVE-2013-1490.

CWE(s)
NVD-CWE-OtherCWE-693
KEV Date Added
25 May 2022

Related Threats

MITRE ATT&CK Enterprise Techniques

T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
attack.mitre.org →
T1553.005 Mark-of-the-Web Bypass Defense Impairment
Adversaries may abuse specific file formats to subvert Mark-of-the-Web (MOTW) controls.
attack.mitre.org →
T1600 Weaken Encryption Defense Impairment
Adversaries may compromise a network device’s encryption capability in order to bypass encryption that would otherwise protect data communications.
attack.mitre.org →
T1689 Downgrade Attack Defense Impairment
Adversaries may downgrade or use a version of system features that may be outdated, vulnerable, and/or does not support updated security controls.
attack.mitre.org →
T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-60166Same product: Oracle Jre
CVE-2026-60164Same product: Oracle Jre
CVE-2024-20923Same product: Oracle Jre
CVE-2026-22013Same product: Oracle Jre
CVE-2013-2465Same product: Oracle Jreboth on KEV
CVE-2019-1003030Shared CWE-693both on KEV
CVE-2025-40536Shared CWE-693both on KEV
CVE-2024-38213Shared CWE-693both on KEV
CVE-2026-21513Shared CWE-693both on KEV
CVE-2024-21412Shared CWE-693both on KEV

Affected Assets

oracle
jre
1.7.0
oracle
openjdk
7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 8 hardening rules · 6 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.3.3
  • V6.6.3
  • V10.2.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

AC-25 Reference Monitor
addresses: CWE-693

Implements a reliable, tamperproof protection mechanism whose completeness can be assured.

AT-1 Policy and Procedures
addresses: CWE-693

Procedures for training on protection mechanisms reduce the chance of protection mechanism failures being present or exploitable.

CA-1 Policy and Procedures
addresses: CWE-693

Documented procedures to implement assessment, authorization, and monitoring controls prevent these protection mechanisms from failing due to undefined processes.

CA-2 Control Assessments
addresses: CWE-693

Direct evaluation of whether controls produce desired security outcomes detects protection mechanism failures and enables remediation.

CA-4 Security Certification
addresses: CWE-693

Requires assessment that protection mechanisms are correctly implemented and producing intended security outcomes.

CA-5 Plan of Action and Milestones
addresses: CWE-693

The POA&M process ensures identified weaknesses in protection mechanisms are documented and scheduled for remediation, reducing the duration they remain exploitable.

CA-7 Continuous Monitoring
addresses: CWE-693

Ongoing control assessments and analysis of monitoring data enable timely detection and response when protection mechanisms fail.

CM-4 Impact Analyses
addresses: CWE-693

Impact analysis identifies changes that could weaken or disable existing protection mechanisms.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

Enforcing authentication directly implements a core protection mechanism whose absence or misuse is the CWE.

PR.AA-05 mostly match
prevents

Defining and enforcing access authorizations is a protection mechanism; proper use prevents the CWE.

PR.DS-01 mostly match
prevents

Cryptographic and integrity controls are protection mechanisms whose correct deployment mitigates the CWE.

PR.DS-02 mostly match
prevents

Encryption and integrity protections for transit are explicit protection mechanisms.

PR.IR-01 mostly match
prevents

Logical network protections are protection mechanisms whose failure matches the CWE.

PR.PS-01 partial match
prevents

Hardened configuration baselines ensure protection mechanisms are correctly applied and maintained.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.36 Compliance with policies, rules and standards for information security partial match
finds

Systematic verification that security mechanisms operate according to defined standards reduces the likelihood that protection mechanisms are bypassed or disabled.

A.8.20 Networks security partial match
mitigates

Hardening devices, disabling vulnerable protocols, and maintaining accurate network diagrams reduce the likelihood that a protection mechanism is misconfigured or left in a weak state.

A.5.24 Information security incident management planning and preparation none match
none

Requiring defined escalation paths, crisis activation criteria, and coordination procedures strengthens the overall protection mechanism so that a single control failure is less likely to leave the organization exposed.

A.5.25 Assessment and decision on information security events none match
none

By requiring a documented categorization and decision process for security events, the control ensures that protection mechanisms are not bypassed or ignored when anomalies occur.

A.5.26 Response to information security incidents none match
none

Identifying and remediating control weaknesses that contributed to an incident reduces the likelihood that protection mechanisms will fail again.

A.5.27 Learning from information security incidents none match
none

Post-incident analysis that feeds updated risk assessments and additional controls directly reduces the chance that previously exploited weaknesses will recur.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-693
  • V-248525 All OL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection. prevents CWE-693
Windows 10 (2 rules)
  • V-220865 The Windows Remote Management (WinRM) service must not use Basic authentication. prevents CWE-693
  • V-220812 Credential Guard must be running on Windows 10 domain-joined systems. prevents CWE-693
Windows 11 (1 rule)
  • V-253418 The Windows Remote Management (WinRM) service must not use Basic authentication. prevents CWE-693
Windows Server 2016 (1 rule)
  • V-225012 Windows Server 2016 must be running Credential Guard on domain-joined member servers. prevents CWE-693
Windows Server 2019 (1 rule)
  • V-205907 Windows Server 2019 must be running Credential Guard on domain-joined member servers. prevents CWE-693
Windows Server 2022 (1 rule)
  • V-254441 Windows Server 2022 must be running Credential Guard on domain-joined member servers. prevents CWE-693

References