CVE-2017-5929: QOS.ch Logback vulnerable to Deserialization of Untrusted Data

CVE-2017-5929 · Severity: low · CVSS 3 · Published 2021-06-07

QOS.ch Logback vulnerable to Deserialization of Untrusted Data

Technologies: ch.qos.logback:logback-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2017-5929 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-5929 being exploited in the wild.
How severe is CVE-2017-5929?
Low severity, with a CVSS score of 3, published 7 June 2021.
Which products and versions are affected?
ch.qos.logback:logback-classic (Maven) ECOSYSTEM:introduced=0,fixed=1.2.0; ch.qos.logback:logback-core (Maven) ECOSYSTEM:introduced=0,fixed=1.2.0.
Is there a fix for CVE-2017-5929?
Yes. ch.qos.logback:logback-classic (Maven): upgrade to 1.2.0 or later; ch.qos.logback:logback-core (Maven): upgrade to 1.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-5929?
Check whether you run ch.qos.logback:logback-classic (Maven) or ch.qos.logback:logback-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • ch.qos.logback:logback-classic (Maven): upgrade to 1.2.0 or later
    # set ch.qos.logback:logback-classic to 1.2.0 in your pom.xml or build.gradle
  • ch.qos.logback:logback-core (Maven): upgrade to 1.2.0 or later
    # set ch.qos.logback:logback-core to 1.2.0 in your pom.xml or build.gradle

Affected products

  • ch.qos.logback:logback-classic (Maven) ECOSYSTEM:introduced=0,fixed=1.2.0
  • ch.qos.logback:logback-core (Maven) ECOSYSTEM:introduced=0,fixed=1.2.0

Identifiers

  • CVE-2017-5929
  • GHSA-vmfg-rjjm-rjrj

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.