CVE-2017-1000208: Deserialization of Untrusted Data in swagger-parser

CVE-2017-1000208 · Severity: low · CVSS 3 · Published 2018-10-19

Deserialization of Untrusted Data in swagger-parser

Technologies: io.swagger:swagger-codegen (Maven). Vendors: Maven.

Quick answers

Is CVE-2017-1000208 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-1000208 being exploited in the wild.
How severe is CVE-2017-1000208?
Low severity, with a CVSS score of 3, published 19 October 2018.
Which products and versions are affected?
io.swagger:swagger-codegen (Maven) ECOSYSTEM:introduced=0,fixed=2.2.2; io.swagger:swagger-parser (Maven) ECOSYSTEM:introduced=0,fixed=1.0.31.
Is there a fix for CVE-2017-1000208?
Yes. io.swagger:swagger-codegen (Maven): upgrade to 2.2.2 or later; io.swagger:swagger-parser (Maven): upgrade to 1.0.31 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-1000208?
Check whether you run io.swagger:swagger-codegen (Maven) or io.swagger:swagger-parser (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

  • io.swagger:swagger-codegen (Maven): upgrade to 2.2.2 or later
    # set io.swagger:swagger-codegen to 2.2.2 in your pom.xml or build.gradle
  • io.swagger:swagger-parser (Maven): upgrade to 1.0.31 or later
    # set io.swagger:swagger-parser to 1.0.31 in your pom.xml or build.gradle

Affected products

  • io.swagger:swagger-codegen (Maven) ECOSYSTEM:introduced=0,fixed=2.2.2
  • io.swagger:swagger-parser (Maven) ECOSYSTEM:introduced=0,fixed=1.0.31

Identifiers

  • CVE-2017-1000208
  • GHSA-q7pf-qr96-2vq5

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