CVE-2011-3544
Published: March 3, 2022
Official Description
An access control vulnerability exists in the Applet Rhino Script Engine component of Oracle's Java Runtime Environment allows an attacker to remotely execute arbitrary code.
CISA KEV Advisory
Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution Vulnerability
An access control vulnerability exists in the Applet Rhino Script Engine component of Oracle's Java Runtime Environment allows an attacker to remotely execute arbitrary code.
Apply updates per vendor instructions.
Risk Analysis
This access control vulnerability in Oracle's Java Runtime Environment's Applet Rhino Script Engine allows remote attackers to execute arbitrary code. Rated as HIGH severity with a very high EPSS score, this indicates a significant likelihood of exploitation. Its presence in CISA's KEV confirms it has been actively exploited.
This vulnerability has been actively exploited in the wild and is part of CISA's KEV, indicating confirmed real-world attacks. The flaw allows for remote code execution.
It is critical to update Oracle Java Runtime Environment to a patched version immediately. Disabling Java applets in web browsers or restricting their execution can also reduce risk.
Technical Analysis
CVE-2011-3544 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2011-3544 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2011-3544 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1