Find, fix and prevent vulnerabilities in your code.
medium severity
new
- Vulnerable module: org.apache.logging.log4j:log4j-core
- Introduced through: org.apache.logging.log4j:log4j-core@2.25.1
Detailed paths
-
Introduced through: robtimus/junit-support@robtimus/junit-support#97ef012e246af39f7b7e3d8db5b43ff78aeac183 › org.apache.logging.log4j:log4j-core@2.25.1Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.25.3.
Overview
org.apache.logging.log4j:log4j-core is a logging library for Java.
Affected versions of this package are vulnerable to Improper Validation of Certificate with Host Mismatch due to the lack of TLS hostname verification in the SocketAppender component. An attacker can intercept or redirect log traffic by performing a man-in-the-middle attack if they are able to intercept or redirect network traffic between the client and the log receiver and can present a server certificate issued by a certification authority trusted by the configured trust store or the default Java trust store.
Workaround
This vulnerability can be mitigated by configuring the SocketAppender to use a private or restricted trust root to limit the set of trusted certificates.
Remediation
Upgrade org.apache.logging.log4j:log4j-core to version 2.25.3 or higher.
References
medium severity
- Vulnerable module: ch.qos.logback:logback-core
- Introduced through: ch.qos.logback:logback-classic@1.5.18
Detailed paths
-
Introduced through: robtimus/junit-support@robtimus/junit-support#97ef012e246af39f7b7e3d8db5b43ff78aeac183 › ch.qos.logback:logback-classic@1.5.18 › ch.qos.logback:logback-core@1.5.18Remediation: Upgrade to ch.qos.logback:logback-classic@1.5.19.
Overview
ch.qos.logback:logback-core is a logback-core module.
Affected versions of this package are vulnerable to External Initialization of Trusted Variables or Data Stores via the conditional processing of the logback.xml configuration file when both the Janino library and Spring Framework are present on the class path. An attacker can execute arbitrary code by compromising an existing configuration file or injecting a malicious environment variable before program execution. This is only exploitable if the attacker has write access to a configuration file or can set a malicious environment variable.
Remediation
Upgrade ch.qos.logback:logback-core to version 1.5.19 or higher.
References
medium severity
- Module: ch.qos.logback:logback-classic
- Introduced through: ch.qos.logback:logback-classic@1.5.18
Detailed paths
-
Introduced through: robtimus/junit-support@robtimus/junit-support#97ef012e246af39f7b7e3d8db5b43ff78aeac183 › ch.qos.logback:logback-classic@1.5.18
Dual license: EPL-1.0, LGPL-2.1
medium severity
- Module: ch.qos.logback:logback-core
- Introduced through: ch.qos.logback:logback-classic@1.5.18
Detailed paths
-
Introduced through: robtimus/junit-support@robtimus/junit-support#97ef012e246af39f7b7e3d8db5b43ff78aeac183 › ch.qos.logback:logback-classic@1.5.18 › ch.qos.logback:logback-core@1.5.18
Dual license: EPL-1.0, LGPL-2.1