Skip to main content
veriom
Menu

Explore Veriom products, resources, and account pages.

CVE-2013-0431Oracle JRE Sandbox Bypass Vulnerability

Patch nowLow3.7Exploited, CISA due date 2022-06-15EPSS 90%, higher than 100% of scored CVEs

CVE-2013-0431 is a protection mechanism failure in Oracle Java Runtime Environment (JRE), rated low (3.7 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

A security control can be bypassed or does not work as intended.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker use a weak default the deployment never changed.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2022-05-25: it is being exploited in the wild. CISA links it to ransomware campaigns. EPSS estimates a 90% chance of exploitation activity in the next 30 days, higher than 100% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2022-06-15.
  2. No fixed version is listed yet. Find every place Oracle Java Runtime Environment (JRE) runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  3. While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  4. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Default settings, permissions and deployment configuration. The flaw sits between the shipped defaults and a hardened deployment.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • Between the shipped defaults and a hardened deployment. An attacker who crosses it can use a weak default the deployment never changed.

Questions to answer about your own systems

  • Where does Oracle Java Runtime Environment (JRE) run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?
See how Veriom maps an architectureTake the interactive tour

Read more

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.