CYBERSECURITYTRACKER
Vulnerabilities

CVE-2021-44832

Apache log4j: Improper Input Validation

What it is

Reported

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

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