CVE-2021-36742
Published: November 3, 2021
Official Description
Trend Micro Apex One, Apex One as a Service, and Worry-Free Business Security contain an improper input validation vulnerability that allows for privilege escalation.
CISA KEV Advisory
Trend Micro Multiple Products Improper Input Validation Vulnerability
Trend Micro Apex One, Apex One as a Service, and Worry-Free Business Security contain an improper input validation vulnerability that allows for privilege escalation.
Apply updates per vendor instructions.
Risk Analysis
This high-severity vulnerability in Trend Micro Apex One, Apex One as a Service, and Worry-Free Business Security allows for privilege escalation due to improper input validation. Its inclusion in CISA's KEV catalog and active exploitation in the wild make it a critical concern, even with a low EPSS score of 0.01869.
This vulnerability is actively being exploited in the wild, as confirmed by its presence in CISA's KEV catalog. Attackers are leveraging this flaw to gain elevated privileges.
Apply the latest security updates for Trend Micro Apex One, Apex One as a Service, and Worry-Free Business Security to address the improper input validation vulnerability. Regularly update all security software to prevent privilege escalation.
Technical Analysis
CVE-2021-36742 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-2021-36742 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.
Exploit & PoC Resources
All References (2)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2021-36742 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