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 15 Jun 2022. Known ransomware use
OpenjdkApplication · Oracle

CVE-2013-0431

MEDIUM · 5.3 CVSS v3.1 Published 2013-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Remotely reachable No privileges Zero-click

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 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 different vulnerability than CVE-2013-1490.

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

This is a Java sandbox bypass vulnerability in the JMX (Java Management Extensions) component of Java SE 7 (through Update 11) and OpenJDK 7. Attackers can exploit unspecified JMX vectors to escape the Java security sandbox, potentially allowing arbitrary code execution. The attack requires user-assisted interaction (CVSS 5.3).

MitigationUpgrade Java SE to Update 15 or later (or the equivalent patched OpenJDK version) to obtain the fix for this JMX sandbox bypass. Remove or disable older, vulnerable Java versions from endpoints and servers.

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
OpenjdkApplication
Affected:= 7
JreApplication
Affected:= 1.7.0

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
Low
Integrity
None
Availability
None

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

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. Identify installed Java version
    Run 'java -version' from command line to retrieve the version string. For Oracle JRE, look for '1.7.0_uXX' where XX is the update number. For OpenJDK, look for '1.7.0' or '7' in the version output.
    Affected if The version shows Java 1.7.0 with update 11 or earlier, or OpenJDK 7 without a newer patch level.
  2. Determine Java vendor and implementation type
    Run 'java -version' and check whether the output indicates Oracle JRE/JDK, OpenJDK, or another distribution. Also check for the presence of java.exe and look at the installation directory structure.
    Affected if The installation is Oracle JRE 1.7.0 through Update 11, or OpenJDK 7 (any sub-version).
  3. Verify JMX service availability
    Check for JMX-related processes or configuration. Look for JMX connectors in application startup scripts, or check if JMX remote ports (typically 1099, 7091, or custom ports) are listening. Inspect configuration files for 'com.sun.management.jmxremote' or similar JMX settings.
    Affected if JMX remote management is enabled and accessible, particularly with authentication disabled or with known default credentials.
  4. Inspect Java deployment configuration
    Check Java Control Panel (Windows) or java deployment properties for JMX-related settings. On systems with multiple Java versions, verify which version is set as the default.
    Affected if The default Java runtime is version 1.7.0 Update 11 or earlier, and JMX is configured for remote access.

A system is affected if it runs any Oracle JRE 1.7.0 through Update 11, or any OpenJDK 7 version, with JMX remote management enabled and accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Java SE to Update 15 or later (or the equivalent patched OpenJDK version) to obtain the fix for this JMX sandbox bypass. Remove or disable older, vulnerable Java versions from endpoints and servers.

Fix this in Openjdk Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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