CVE-2021-448326.6MediumCWE-20

CVE-2021-44832: Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration

Apache Software Foundation · Apache Log4j2

Vendor fix available · Affected: Apache Software Foundation Apache Log4j2 · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

97.9%probability of exploitation in the next 30 days

99th percentile

050100

Higher than 99% of scored CVEs

6.6MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Apache Software Foundation · Apache Log4j2from log4j-core before 2.17.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Input Validation · Input Validation and Logic
Vendor: Apache Software Foundation
Published: December 2021
Band: Likely to be exploited (10% or more), December 2021

CoverageNo articles yet

No CyberSIXT article names CVE-2021-44832 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.