CVE Vulnerabilities

CVE-2016-6814

Deserialization of Untrusted Data

Published: Jan 18, 2018 | Modified: Nov 21, 2024
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
9.6 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

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.

Weakness

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Affected Software

NameVendorStart VersionEnd Version
GroovyApache1.7.0 (including)2.4.3 (including)
GroovyApache2.4.4 (including)2.4.7 (including)
Red Hat Enterprise Linux 7RedHatgroovy-0:1.8.9-8.el7_4*
Red Hat JBoss A-MQ 6.3RedHat*
Red Hat JBoss Data Virtualization 6.3RedHatgroovy*
Red Hat JBoss Fuse 6.3RedHat*
Red Hat Software Collections for Red Hat Enterprise Linux 6RedHatrh-maven33-groovy-0:1.8.9-7.19.el6*
Red Hat Software Collections for Red Hat Enterprise Linux 6.7 EUSRedHatrh-maven33-groovy-0:1.8.9-7.19.el6*
Red Hat Software Collections for Red Hat Enterprise Linux 7RedHatrh-maven33-groovy-0:1.8.9-7.19.el7*
Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUSRedHatrh-maven33-groovy-0:1.8.9-7.19.el7*
GroovyUbuntuesm-apps/xenial*
GroovyUbuntuprecise*
GroovyUbuntutrusty*
GroovyUbuntuupstream*
GroovyUbuntuxenial*
GroovyUbuntuyakkety*
Groovy2Ubuntuesm-apps/xenial*
Groovy2Ubuntuxenial*

Potential Mitigations

  • Make fields transient to protect them from deserialization.
  • An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.

References