← back
CVE-2021-44832mediumobserved exploitationCWE-20CWE-74

Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration

57Vexday Risk Score

Prioritize patching. It exploitation observed by VulnCheck.

ssvc Actcvss 6.6epss 98%
from disclosure to weapon
Published on NVDDec 28
VulnCheck+413d
exploitation probability
98%top 1% of all CVEs
observed exploitation
yesVulnCheck
In short

Apache Log4j2 can execute arbitrary code if an attacker controls the LDAP server used by the application's logging configuration. This happens through the JDBC Appender feature, which improperly validates data source names.

Technical detail

Log4j2 versions 2.0-beta7 through 2.17.0 are vulnerable to RCE via JNDI injection in JDBC Appender configurations. When a LDAP data source URI is specified and an attacker controls the target LDAP server, malicious code can be injected and executed. The vulnerability stems from insufficient input validation (CWE-20) and improper neutralization of special elements (CWE-74) in data source names.

Summary generated and translated by AI from the official description.
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.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H