Homepage

Deserialization of Untrusted Data Affecting groovy-javadoc package, versions <0:1.8.9-8.el7_4

Severity

 Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
3.3% (92nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-GROOVYJAVADOC-4734139
  • published26 Jul 2021
  • disclosed14 Jan 2017
Report a new vulnerability Found a mistake?

Introduced: 14 Jan 2017

CVE-2016-6814  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade RHEL:7 groovy-javadoc to version 0:1.8.9-8.el7_4 or higher.
This issue was patched in RHSA-2017:2486.

NVD Description

Note: Versions mentioned in the description apply only to the upstream groovy-javadoc package and not the groovy-javadoc package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

When an application with unsupported Codehaus versions of Groovy from 1.7.0 to 2.4.3, Apache Groovy 2.4.4 to 2.4.7 on classpath uses standard Java serialization mechanisms, e.g. to communicate between servers or to store local data, it was possible for an attacker to bake a special serialized object that will execute code directly when deserialized. All applications which rely on serialization and do not isolate the code which deserializes objects were subject to this vulnerability.

References