ch.qos.logback:logback-classic@1.1.1 vulnerabilities

Direct Vulnerabilities

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

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • H
Uncontrolled Resource Consumption ('Resource Exhaustion')

ch.qos.logback:logback-classic is a reliable, generic, fast and flexible logging library for Java.

Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') via the logback receiver component. An attacker can mount a denial-of-service attack by sending poisoned data.

Note:

Successful exploitation requires the logback-receiver component being enabled and also reachable by the attacker.

How to fix Uncontrolled Resource Consumption ('Resource Exhaustion')?

Upgrade ch.qos.logback:logback-classic to version 1.2.13, 1.3.14, 1.4.14 or higher.

[,1.2.13) [1.3.0,1.3.14) [1.4.0,1.4.14)
  • H
Denial of Service (DoS)

ch.qos.logback:logback-classic is a reliable, generic, fast and flexible logging library for Java.

Affected versions of this package are vulnerable to Denial of Service (DoS). An attacker can mount a denial-of-service attack by sending poisoned data. This is only exploitable if logback receiver component is deployed.

How to fix Denial of Service (DoS)?

Upgrade ch.qos.logback:logback-classic to version 1.2.13, 1.3.12, 1.4.12 or higher.

[,1.2.13) [1.3.0-alpha0,1.3.12) [1.4.0,1.4.12)
  • C
Arbitrary Code Execution

ch.qos.logback:logback-classic is a reliable, generic, fast and flexible logging library for Java.

Affected versions of this package are vulnerable to Arbitrary Code Execution. A configuration can be turned on to allow remote logging through interfaces that accept untrusted serialized data. Authenticated attackers on the adjacent network can exploit this vulnerability to run arbitrary code through the deserialization of custom gadget chains.

How to fix Arbitrary Code Execution?

Upgrade ch.qos.logback:logback-classic to version 1.2.0 or higher.

[0.3,1.2.0)