Skip to main content
Mallory
LowExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2013-2423: HotSpot permission-check bypass in Oracle Java and OpenJDK 7

Published Apr 17, 2013 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS3.7Low · v3.1
EPSS85.2%100th percentile
CISA KEVYesAdded May 25, 2022
In the wildActivePer CISA KEV
Vendors
Oracle CorporationOpensuseCanonical
IdentifiersCVE-2013-2423CWE-843

CVE-2013-2423 affects the HotSpot component of Oracle Java SE 7 Update 17 and earlier and OpenJDK 7, allowing remote attackers to affect integrity. The original researcher described a MethodHandles permission-check bypass using reflection and type confusion to modify arbitrary public final fields, demonstrated with integer and double fields to disable the Java security manager. Oracle did not confirm those technical claims. Exploit-kit analyses also associated this CVE with bypassing Java security warnings through crafted JNLP content. The vulnerability was exploited by browser exploit kits and in the Sunshop Campaign.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote exploitation can compromise integrity. The researcher-reported mechanism permits modification of public final fields and disabling of the Java security manager, undermining Java permission enforcement; those details were not confirmed by Oracle. Observed exploitation delivered the 9002 remote-access Trojan to victim systems.

Mitigation

If you can’t patch tonight, do this now.

Disable or remove the Java browser plugin and prevent execution of untrusted Java applets and JNLP applications. Where Java cannot be removed, enforce application allowlisting and centrally managed Java security settings, restrict users from approving untrusted Java content, and use browser or endpoint controls to block active content from untrusted sites.

Remediation

Patch, then assume compromise.

Apply the Java security updates addressing CVE-2013-2423, released in April 2013, following vendor instructions. Update affected Oracle Java and OpenJDK installations to a supported release containing the fix. An exact fixed version is not identified in the available vulnerability-specific information.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
CanonicalUbuntu Linuxoperating_system
OpensuseOpensuseoperating_system
Oracle CorporationJreapplication
FAQ

Frequently asked questions

Is CVE-2013-2423 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on May 25, 2022.
Is there a public exploit for CVE-2013-2423?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2013-2423, the earliest disclosed Jan 10, 2013.
Is there a patch for CVE-2013-2423?
Apply the Java security updates addressing CVE-2013-2423, released in April 2013, following vendor instructions. Update affected Oracle Java and OpenJDK installations to a supported release containing the fix.
What products are affected by CVE-2013-2423?
Oracle Corporation Jre, Opensuse, and Canonical Ubuntu Linux.
How severe is CVE-2013-2423?
CVE-2013-2423 has a CVSS v3.1 score of 3.7 (Low) and an EPSS score of 85.2% (100th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware4Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.