CVE-2016-6814: Deserialization of Untrusted Data in Groovy

CVE-2016-6814 · Severity: low · CVSS 3 · Published 2022-05-13

Deserialization of Untrusted Data in Groovy

Technologies: org.codehaus.groovy:groovy (Maven), org.codehaus.groovy:groovy-all (Maven). Vendors: Maven.

Quick answers

Is CVE-2016-6814 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-6814 being exploited in the wild.
How severe is CVE-2016-6814?
Low severity, with a CVSS score of 3, published 13 May 2022.
Which products and versions are affected?
org.codehaus.groovy:groovy (Maven) ECOSYSTEM:introduced=1.7.0,fixed=2.4.8; org.codehaus.groovy:groovy-all (Maven) ECOSYSTEM:introduced=1.7.0,fixed=2.4.8.
Is there a fix for CVE-2016-6814?
Yes. org.codehaus.groovy:groovy (Maven): upgrade to 2.4.8 or later; org.codehaus.groovy:groovy-all (Maven): upgrade to 2.4.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-6814?
Check whether you run org.codehaus.groovy:groovy (Maven) or org.codehaus.groovy:groovy-all (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

  • org.codehaus.groovy:groovy (Maven): upgrade to 2.4.8 or later
    # set org.codehaus.groovy:groovy to 2.4.8 in your pom.xml or build.gradle
  • org.codehaus.groovy:groovy-all (Maven): upgrade to 2.4.8 or later
    # set org.codehaus.groovy:groovy-all to 2.4.8 in your pom.xml or build.gradle

Affected products

  • org.codehaus.groovy:groovy (Maven) ECOSYSTEM:introduced=1.7.0,fixed=2.4.8
  • org.codehaus.groovy:groovy-all (Maven) ECOSYSTEM:introduced=1.7.0,fixed=2.4.8

Identifiers

  • CVE-2016-6814
  • GHSA-xphj-m9cc-8fmq

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