ch.qos.logback:logback-core vulnerabilities
logback-core module
- Registry
- Maven
- Latest
- 1.6.7
10 known advisories
The latest version, 1.6.7, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=ch.qos.logback:logback-core -DdepVersion=1.6.7 -DforceVersion=trueIs your project on an affected ch.qos.logback:logback-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for ch.qos.logback:logback-core
Logback vulnerable to Object Injection through HardenedObjectInputStream modules
- Affected
- <1.5.34
- Fixed in
- 1.5.34
QOS.CH Sarl logback logback-core has a deserialization of untrusted data vulnerability
- Affected
- <1.5.33
- Fixed in
- 1.5.33
Logback allows an attacker to instantiate classes already present on the class path
- Affected
- <1.5.25
- Fixed in
- 1.5.25
QOS.CH logback-core is vulnerable to Arbitrary Code Execution through file processing
- Affected
- >=1.4.0 <1.5.19 · <1.3.16
- Fixed in
- 1.3.16, 1.5.19
QOS.CH logback-core Expression Language Injection vulnerability
- Affected
- >=1.4.0 <1.5.13 · <1.3.15
- Fixed in
- 1.3.15, 1.5.13
QOS.CH logback-core Server-Side Request Forgery vulnerability
- Affected
- >=1.4.0 <1.5.13 · <1.3.15
- Fixed in
- 1.3.15, 1.5.13
Logback is vulnerable to an attacker mounting a Denial-Of-Service attack by sending poisoned data
- Affected
- >=1.4.13 <1.4.14 · >=1.3.13 <1.3.14 · >=1.2.12 <1.2.13
- Fixed in
- 1.2.13, 1.3.14, 1.4.14
logback serialization vulnerability
- Affected
- >=1.3.0 <1.3.12 · >=1.4.0 <1.4.12 · <1.2.13
- Fixed in
- 1.2.13, 1.3.12, 1.4.12
Deserialization of Untrusted Data in logback
- Affected
- <1.2.9
- Fixed in
- 1.2.9
QOS.ch Logback vulnerable to Deserialization of Untrusted Data
- Affected
- <1.2.0
- Fixed in
- 1.2.0
Is your ch.qos.logback:logback-core version vulnerable?
- ch.qos.logback:logback-core 1.6No known advisories in 1.6.7
- ch.qos.logback:logback-core 1.5No known advisories in 1.5.38
- ch.qos.logback:logback-core 1.46 advisories in 1.4.14
- ch.qos.logback:logback-core 1.33 advisories in 1.3.16
- ch.qos.logback:logback-core 1.26 advisories in 1.2.13
- ch.qos.logback:logback-core 1.19 advisories in 1.1.11
- ch.qos.logback:logback-core 0.99 advisories in 0.9.30
- ch.qos.logback:logback-core 0.89 advisories in 0.8.1
- ch.qos.logback:logback-core 0.79 advisories in 0.7.1
- ch.qos.logback:logback-core 0.69 advisories in 0.6.0
- ch.qos.logback:logback-core 0.59 advisories in 0.5.0
- ch.qos.logback:logback-core 0.39 advisories in 0.3.0
Which of your client projects still run an old ch.qos.logback:logback-core?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.