CVE-2016-4437
Published: November 3, 2021
Official Description
Apache Shiro contains a vulnerability which may allow remote attackers to execute code or bypass intended access restrictions via an unspecified request parameter when a cipher key has not been configured for the "remember me" feature.
CISA KEV Advisory
Apache Shiro Code Execution Vulnerability
Apache Shiro contains a vulnerability which may allow remote attackers to execute code or bypass intended access restrictions via an unspecified request parameter when a cipher key has not been configured for the "remember me" feature.
Apply updates per vendor instructions.
Risk Analysis
Apache Shiro has a vulnerability that allows remote attackers to execute code or bypass access restrictions if the 'remember me' feature's cipher key is not configured. With an EPSS score of 0.94214 and inclusion in the KEV, this flaw is highly likely to be exploited.
This vulnerability is actively exploited in the wild. The ability to execute code or bypass access restrictions remotely makes it a significant threat.
Ensure that a strong, unique cipher key is configured for the 'remember me' feature in Apache Shiro. Apply any available patches or updates for Apache Shiro to mitigate this vulnerability.
Technical Analysis
CVE-2016-4437 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-2016-4437 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-2016-4437 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