CVE-2021-45105
Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.
A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.
Detection and validation
Mapped metadata availability only. These signals do not change priority.
Sigma
Not mapped by tracked sources.
Atomic
Not mapped by tracked sources.
Nuclei
Not mapped by tracked sources.
What it is
ReportedApache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
Source reported · Source: NVD · Source last published: · Source description excerpt; complete tracked detail loads below. · Source last updated: · Tracker data as of:
What is affected
ReportedApache; log4j. Product-level identification only; no affected-version conclusion is available from this field.
Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:
Urgency and basis
ReportedAct now · 554.2
Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:
Exploitation evidence
Reportedlisted by a tracked exploitation catalog · VulnCheck KEV
Source reported · VulnCheck KEV added: · Source last updated: · Tracker data as of:
What to do
ReportedApply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Source remediation ↗Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:
Evidence detail
Loading the full tracker evidence record…