Skip to content

spring-boot-starter-log4j2-2.6.1.jar: 3 vulnerabilities (highest severity is: 10.0) [main] (reachable) #6

Open
Open
spring-boot-starter-log4j2-2.6.1.jar: 3 vulnerabilities (highest severity is: 10.0) [main] (reachable)#6
@mend-developer-platform-dev

Description

@mend-developer-platform-dev
mend-developer-platform-dev
bot
opened on Sep 28, 2025
📂 Vulnerable Library - spring-boot-starter-log4j2-2.6.1.jar

Starter for using Log4j2 for logging. An alternative to spring-boot-starter-logging

Path to dependency file: /build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.springframework.boot/spring-boot-starter-log4j2/2.6.1/3d65aa0e022cedbb7f639add91b62f8f34e94409/spring-boot-starter-log4j2-2.6.1.jar

Findings

Finding Severity 🎯 CVSS Exploit Maturity EPSS Library Type Fixed in Remediation Available Reachability
CVE-2021-44228 🟣 Critical 10.0 High 94.4% log4j-core-2.14.1.jar Transitive N/A ❌ Reachable
CVE-2021-45046 🟣 Critical 9.5 High 94.3% log4j-core-2.14.1.jar Transitive N/A ❌ Reachable
CVE-2021-44832 🔴 High 7.5 High 35.2% log4j-core-2.14.1.jar Transitive N/A ❌ Reachable

Details

🟣CVE-2021-44228

Vulnerable Library - log4j-core-2.14.1.jar

The Apache Log4j Implementation

Library home page: https://www.apache.org/

Path to dependency file: /build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar

Dependency Hierarchy:

  • spring-boot-starter-log4j2-2.6.1.jar (Root Library)
    • ❌ log4j-core-2.14.1.jar (Vulnerable Library)

Reachability Analysis

This vulnerability is potentially reachable:

- fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
    - org.springframework.boot.SpringApplication (Extension)
        - org.springframework.boot.web.servlet.support.SpringBootServletInitializer$WebEnvironmentPropertySourceInitializer (Extension)
            - org.springframework.boot.web.servlet.support.SpringBootServletInitializer (Extension)
                - org.springframework.boot.context.logging.LoggingApplicationListener (Extension)
                    - org.springframework.boot.logging.log4j2.Log4J2LoggingSystem (Extension)
                        -> ❌ org.apache.logging.log4j.core.Logger (Vulnerable Component)

Vulnerability Details

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

Publish Date: Dec 10, 2021 12:00 AM

URL: CVE-2021-44228

Threat Assessment

Exploit Maturity:High

EPSS:94.4%

Score: 10.0

Suggested Fix

Type: Upgrade version

Origin:

Release Date:

Fix Resolution :

🟣CVE-2021-45046

Vulnerable Library - log4j-core-2.14.1.jar

The Apache Log4j Implementation

Library home page: https://www.apache.org/

Path to dependency file: /build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar

Dependency Hierarchy:

  • spring-boot-starter-log4j2-2.6.1.jar (Root Library)
    • ❌ log4j-core-2.14.1.jar (Vulnerable Library)

Reachability Analysis

This vulnerability is potentially reachable:

- fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
    - org.springframework.boot.SpringApplication (Extension)
        - org.springframework.boot.web.servlet.support.SpringBootServletInitializer$WebEnvironmentPropertySourceInitializer (Extension)
            - org.springframework.boot.web.servlet.support.SpringBootServletInitializer (Extension)
                - org.springframework.boot.context.logging.LoggingApplicationListener (Extension)
                    - org.springframework.boot.logging.log4j2.Log4J2LoggingSystem (Extension)
                        - org.apache.logging.log4j.core.LoggerContext (Extension)
                            - org.apache.logging.log4j.core.filter.MapFilter (Extension)
                                - org.apache.logging.log4j.core.config.plugins.PluginAttribute (Extension)
                                    - org.apache.logging.log4j.core.config.plugins.visitors.PluginAttributeVisitor (Extension)
                                        - org.apache.logging.log4j.core.layout.AbstractJacksonLayout$ReadOnlyLogEventWrapper (Extension)
                                            - org.apache.logging.log4j.core.layout.AbstractJacksonLayout (Extension)
                                                - org.apache.logging.log4j.core.layout.PatternLayout$PatternSerializer (Extension)
                                                    - org.apache.logging.log4j.core.layout.PatternLayout (Extension)
                                                        -> ❌ org.apache.logging.log4j.core.pattern.MessagePatternConverter (Vulnerable Component)

Vulnerability Details

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.

Publish Date: Dec 14, 2021 04:55 PM

URL: CVE-2021-45046

Threat Assessment

Exploit Maturity:High

EPSS:94.3%

Score: 9.5

Suggested Fix

Type: Upgrade version

Origin:

Release Date:

Fix Resolution :

🔴CVE-2021-44832

Vulnerable Library - log4j-core-2.14.1.jar

The Apache Log4j Implementation

Library home page: https://www.apache.org/

Path to dependency file: /build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j/log4j-core/2.14.1/9141212b8507ab50a45525b545b39d224614528b/log4j-core-2.14.1.jar

Dependency Hierarchy:

  • spring-boot-starter-log4j2-2.6.1.jar (Root Library)
    • ❌ log4j-core-2.14.1.jar (Vulnerable Library)

Reachability Analysis

This vulnerability is potentially reachable:

- fr.christophetd.log4shell.vulnerableapp.VulnerableAppApplication (Application)
    - org.springframework.boot.SpringApplication (Extension)
        - org.springframework.boot.web.servlet.support.SpringBootServletInitializer$WebEnvironmentPropertySourceInitializer (Extension)
            - org.springframework.boot.web.servlet.support.SpringBootServletInitializer (Extension)
                - org.springframework.boot.context.logging.LoggingApplicationListener (Extension)
                    - org.springframework.boot.logging.log4j2.Log4J2LoggingSystem (Extension)
                        - org.apache.logging.log4j.core.config.Configuration (Extension)
                            - org.apache.logging.log4j.core.appender.db.jdbc.JdbcAppender (Extension)
                                -> ❌ org.apache.logging.log4j.core.appender.db.jdbc.DataSourceConnectionSource (Vulnerable Component)

Vulnerability Details

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.

Publish Date: Dec 28, 2021 07:35 PM

URL: CVE-2021-44832

Threat Assessment

Exploit Maturity:High

EPSS:35.2%

Score: 7.5

Suggested Fix

Type: Upgrade version

Origin:

Release Date:

Fix Resolution :

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions