CYBERSECURITYTRACKER
Vulnerabilities

CVE-2021-45105

Apache log4j: Improper Input Validation

What it is

Reported

Apache 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 · Complete source description.
Dates
Source last published: · Source last updated:

What is affected

Reported

Apache; log4j. Product-level identification only; no affected-version conclusion is available from this field.

Source reported · Source: NVD
Dates
Source last published: · Source last updated:

Urgency and basis

Tracker computed

Act now

Current priority score and EPSS: loading from the tracker record. They are read when this page loads and are not shown without JavaScript. They change daily and are not part of "Source last updated".

Tracker decision tier from the evidence detailed below
Dates
Source last updated:

Exploitation evidence

Reported

listed by a tracked exploitation catalog · VulnCheck KEV

Source reported
Dates
VulnCheck KEV added: · Source last updated:

What to do

Reported

Apply 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
Dates
Source last updated:

Detection and validation

Mapped metadata availability only. These signals do not change priority.

Sigma, Atomic, Nuclei, and Metasploit: none mapped by tracked sources.

  • Sigma

    Not mapped by tracked sources.

  • Atomic

    Not mapped by tracked sources.

  • Nuclei

    Not mapped by tracked sources.

  • Metasploit

    Not mapped by tracked sources.

Evidence detail

Loading the full tracker evidence record…

Glossary

Open in glossary