CVE-2021-44228 remediation guide

Identify the affected asset

Confirm whether Apache Log4j2 is installed, record the deployed version and installation path, and identify exposed interfaces.

• Record the product name, package or appliance identifier, and installed version.
• Identify internet-facing, administrative, API, and internal access paths.
• Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: 2.0-beta9, < 2.7.0, >= 2.0.1 < 2.3.1, >= 2.4.0 < 2.12.2, >= 2.13.0 < 2.15.0, 2.0, < 2019.1, 2019.1, < 10.4.2, 3.0, 4.0, 4.1, 4.2, 5.0, 5.1, < 2021-12-13, 3.1, 8.5, 8.6, 8.7. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

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.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

• Confirm the expected version and package state.
• Run a functional health check for critical service paths.
• Review authentication, error, application, and security monitoring logs.
• Reassess exposure if the supported fix cannot be applied.