Skip to content

CVE-2021-44228

Log4Shell

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

CVSS
10.0Criticalscored by CISA
Exploited in the wild
Yes, in CISA KEV since 10 Dec 2021CISA deadline for US federal agencies: 24 Dec 2021known use in ransomware campaignspublic exploit code
EPSS
> 99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
10 Dec 2021analysed here 12 Nov 2026

Do first. 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's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weaknesses
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Apache Software Foundation Apache Log4j2>= 2.0-beta9 and < log4j-core*Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • siemens:6bk1602-0aa12-0tp0_firmware
  • siemens:6bk1602-0aa22-0tp0_firmware
  • siemens:6bk1602-0aa32-0tp0_firmware
  • siemens:6bk1602-0aa42-0tp0_firmware
  • siemens:6bk1602-0aa52-0tp0_firmware
  • apache:log4j
  • siemens:sppa-t3000_ses3000_firmware
  • siemens:capital
  • siemens:comos
  • siemens:desigo_cc_advanced_reports
  • siemens:desigo_cc_info_center
  • siemens:e-car_operation_center
  • siemens:energy_engage
  • siemens:energyip
  • siemens:energyip_prepay
  • siemens:gma-manager
  • siemens:head-end_system_universal_device_integration_system
  • siemens:industrial_edge_management
  • siemens:industrial_edge_management_hub
  • siemens:logo\!_soft_comfort
  • siemens:mendix
  • siemens:mindsphere
  • siemens:navigator
  • siemens:nx
  • siemens:opcenter_intelligence
  • siemens:operation_scheduler
  • siemens:sentron_powermanager
  • siemens:siguard_dsa
  • siemens:sipass_integrated
  • siemens:siveillance_command

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. AWS WAF, Azure WAF and Google Cloud Armor publish WAF rules written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode · rate limit · CDN · allow-list classes

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 10 Dec 2021. Known use in ransomware campaigns.
CISA due date
24 Dec 2021, the remediation deadline for US federal agencies
CISA 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.
Public exploit code
Yes: 3 on Exploit-DB · 5 Metasploit modules · 507 GitHub proofs of concept · 1 Nuclei template
CISA SSVC
exploitation active, automatable yes, technical impact totalAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 9 Dec 2021First public exploit or proof of concept
  2. 10 Dec 2021Added to CISA KEV (exploited in the wild)1 day later
  3. 10 Dec 2021Publishedsame day later
  4. 24 Dec 2021CISA remediation due date (US federal agencies)14 days later
  5. 4 Feb 2025CISA SSVC assessment: exploitation active1,139 days (about 3 years) later
  6. 21 Oct 2025CVE record last updated259 days (about 9 months) later
  7. 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeChangedImpact crosses a security boundary into other components.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2021-44228 being exploited?

Yes. CVE-2021-44228 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2021-44228?

CVE-2021-44228 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2021-44228?

Yes. A fix has been recorded for CVE-2021-44228. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2021-44228 affect?

CVE-2021-44228 affects siemens:6bk1602-0aa12-0tp0_firmware, siemens:6bk1602-0aa22-0tp0_firmware, siemens:6bk1602-0aa32-0tp0_firmware, siemens:6bk1602-0aa42-0tp0_firmware, and 26 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

50 references in the CVE record, grouped by the tags the record gives them.

Advisories (6)

Other links (44)

Show 38 more

Also tracked as GHSA-jfh8-c2jp-5v3q (OSV).

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com