ch.qos.logback:logback-core 1.3.16

Direct Vulnerabilities

Known vulnerabilities in the ch.qos.logback:logback-core package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
M Deserialization of Untrusted Data ch.qos.logback:logback-core is a logback-core module. Affected versions of this package are vulnerable to Deserialization of Untrusted Data in `HardenedObjectInputStream`, whose `resolveClass` allowlist admitted any class whose name starts with `java.lang` or `java.util` rather than matching specific authorized classes. An attacker can instantiate dangerous classes such as `java.lang.ProcessBuilder` during deserialization, reaching remote code execution through a gadget chain, by delivering a malicious serialized object to a logback component that deserializes it, such as its socket receiver for serialized logging events (`SocketNode`). Exploitation requires the application to deserialize attacker-controlled serialized data through logback, in practice via its socket-based receiver, together with a usable gadget class on the classpath. How to fix Deserialization of Untrusted Data? Upgrade `ch.qos.logback:logback-core` to version 1.5.33 or higher.	[,1.5.33)
H Expression Injection ch.qos.logback:logback-core is a logback-core module. Affected versions of this package are vulnerable to Expression Injection in the Janino-evaluated `condition` attribute of `<if>` configuration elements, handled by `IfModelHandler`, whose denylist blocked only the literal `new` operator. A user who can modify the logback configuration can execute arbitrary code by writing an `<if>` condition that evades that denylist, either through references it did not cover such as `Runtime` or `springframework`, or through Unicode escape sequences like `\u` that reconstruct the blocked `new` operator. Exploitation requires write access to the logback configuration and the use of conditional `<if>` processing with Janino present on the classpath. How to fix Expression Injection? Upgrade `ch.qos.logback:logback-core` to version 1.5.36 or higher.	[0.9.20,1.5.36)
L External Initialization of Trusted Variables or Data Stores 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 during the configuration file processing. An attacker can instantiate arbitrary classes already present on the class path by compromising an existing configuration file. How to fix External Initialization of Trusted Variables or Data Stores? Upgrade `ch.qos.logback:logback-core` to version 1.5.25 or higher.	[0.9.20,1.5.25)

Vulnerability

Vulnerable Version

Deserialization of Untrusted Data

ch.qos.logback:logback-core is a logback-core module.

Affected versions of this package are vulnerable to Deserialization of Untrusted Data in HardenedObjectInputStream, whose resolveClass allowlist admitted any class whose name starts with java.lang or java.util rather than matching specific authorized classes. An attacker can instantiate dangerous classes such as java.lang.ProcessBuilder during deserialization, reaching remote code execution through a gadget chain, by delivering a malicious serialized object to a logback component that deserializes it, such as its socket receiver for serialized logging events (SocketNode). Exploitation requires the application to deserialize attacker-controlled serialized data through logback, in practice via its socket-based receiver, together with a usable gadget class on the classpath.

How to fix Deserialization of Untrusted Data?

Upgrade ch.qos.logback:logback-core to version 1.5.33 or higher.

[,1.5.33)

Expression Injection

ch.qos.logback:logback-core is a logback-core module.

Affected versions of this package are vulnerable to Expression Injection in the Janino-evaluated condition attribute of <if> configuration elements, handled by IfModelHandler, whose denylist blocked only the literal new operator. A user who can modify the logback configuration can execute arbitrary code by writing an <if> condition that evades that denylist, either through references it did not cover such as Runtime or springframework, or through Unicode escape sequences like \u that reconstruct the blocked new operator. Exploitation requires write access to the logback configuration and the use of conditional <if> processing with Janino present on the classpath.

How to fix Expression Injection?

Upgrade ch.qos.logback:logback-core to version 1.5.36 or higher.

[0.9.20,1.5.36)

External Initialization of Trusted Variables or Data Stores

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 during the configuration file processing. An attacker can instantiate arbitrary classes already present on the class path by compromising an existing configuration file.

How to fix External Initialization of Trusted Variables or Data Stores?

Upgrade ch.qos.logback:logback-core to version 1.5.25 or higher.

[0.9.20,1.5.25)

ch.qos.logback:logback-core@1.3.16

latest version

latest non vulnerable version

first published

latest version published

licenses detected

package registry

Direct Vulnerabilities

Fix vulnerabilities automatically