Apache Log4j2 Remote Code Execution
What to do
For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.
CISA deadline 2021-12-24 · passed 4 years 8 months ago · applies to US federal civilian agencies; used elsewhere as a reference SLA
What happened
Apache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution.
Who is affected
Apache Log4j2. Affected version ranges are listed in the vendor advisory and the NVD entry linked under Sources.
Weakness class: CWE-20, CWE-400, CWE-502.
Timeline
- Added to CISA KEVExploitation in the wild confirmed by CISA
- CISA remediation deadlinepassed 4 years 8 months ago
Sources
- NVD entry for CVE-2021-44228 nvd.nist.gov/vuln/detail/CVE-2021-44228
- CISA Known Exploited Vulnerabilities catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
- nvd.nist.gov nvd.nist.gov/vuln/detail/CVE-2021-44228