No. CVE-2021-44228
A Apache Log4j2 bug is being used in attacks
Yes. Attackers are using this right now.
What to do
Apply the vendor's update. If there is none, stop using it or cut it off from the internet.
- Confirmed in attacks
- Dec 10, 2021
- Product
- Apache Log4j2
- Ransomware
- Used by gangs
- Attack likelihood, next 30 days
- over 99%
Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.
The official description
Apache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution.
Required action: 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.
For your tech helper
A read-only checklist for whoever helps you with your computer, or an AI assistant. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.
Read-only check, change nothing, send nothing anywhere.
Is Apache Log4j2 (CVE-2021-44228) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2021-44228. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.