Lack of data validation In org.apache.logging.log4j:log4j-api
Description
Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3) 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 and 2.12.3.
Affected packages
Only the org.apache.logging.log4j:log4j-core package is directly affected by this vulnerability. The org.apache.logging.log4j:log4j-api should be kept at the same version as the org.apache.logging.log4j:log4j-core package to ensure compatability if in use.
Mitigation
Update Impact
Minimal update. May introduce new vulnerabilities or breaking changes.
Ecosystem | Package | Affected version | Patched versions |
|---|---|---|---|
maven | 2.12.3, 2.17.0 | ||
maven | 2.12.3, 2.17.0, 2.3.1 | ||
maven | 1.9.2, 1.10.9, 1.11.12, 2.0.13 | ||
debian 11 | 2.17.0-1~deb11u1 | ||
debian 13 | 2.17.0-1 | ||
debian 14 | 2.17.0-1 | ||
debian 12 | 2.17.0-1 |
Aliases
References