CVE Tools

CVE-2013-0431

Exploited in the wild. In CISA KEV since 2022‑05‑25. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Red Hat Inc. Red Hat Enterprise Linux ServerAffected: 6Upgrade to: not statedAffected: 5.9Upgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat Enterprise Linux WorkstationAffected: 6.0Upgrade to: not statedStated by: BDU
  • Oracle Corp. Java Runtime EnvironmentAffected: до 7 Update 11 включительноUpgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether any computers or servers run Java Runtime Environment 7 through Update 11 or OpenJDK 7.
  2. Upgrade Oracle Java SE 7 to Update 13 or later; for OpenJDK 7, install the security update supplied by your operating-system vendor.
  3. Remove Java 7 where it is no longer required, especially from employee computers.
  4. Ask IT to check for suspicious Java activity on systems that were unpatched.

Coverage timeline

0 publishers
  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

Businesses using Java Runtime Environment 7 through Update 11, or OpenJDK 7, should act now because criminals have used this flaw to get around Java’s built-in safety controls.

User-assisted sandbox bypass in JRE/OpenJDK 7 related to JMX, enabling remote attackers to escape Java security restrictions through unspecified vectors.

If you're affected

  • Malware installation risk
  • Ransomware exposure
  • Data theft risk
  • Business disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2022-05-25.

US federal agencies must remediate by 2022-06-15.

Known use in ransomware campaigns.

Apply updates per vendor instructions.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

90% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

16 events over 4992 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. EPSS band changehigh → critical
  4. EPSS band changehigh → criticalepss band change
  5. Patch availablerecord updated
  6. OpenVAS check added

Affected products

Technical detail

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

Scored 3.7 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Jre, not every advisory. This one: actively exploited.