Homepage
About Snyk

Expression Language Injection Affecting apache-log4j2 package, versions <2.16.0-1~deb10u1

0.0
critical

Snyk CVSS

    Attack Complexity High
    Scope Changed
    Confidentiality High
    Integrity High
    Availability High

    Threat Intelligence

    Exploit Maturity Mature
    EPSS 97.36% (100th percentile)
Expand this section
NVD
9 critical
Expand this section
Red Hat
8.1 high

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-DEBIAN10-APACHELOG4J2-2320108
  • published 15 Dec 2021
  • disclosed 14 Dec 2021
Report a new vulnerability Found a mistake?

Introduced: 14 Dec 2021

CVE-2021-45046 Open this link in a new tab
CWE-917 Open this link in a new tab

How to fix?

Upgrade Debian:10 apache-log4j2 to version 2.16.0-1~deb10u1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream apache-log4j2 package and not the apache-log4j2 package as distributed by Debian. See How to fix? for Debian:10 relevant fixed versions and status.

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

References