UBUNTU-CVE-2016-6814: Critical severity ubuntu/groovy2 vulnerability

Published Jan 18, 2018
·
Updated

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.

Affected Software

2 affected componentsFixes available
ubuntu/groovy2<2.4.5-1ubuntu0.1~esm1
2.4.5-1ubuntu0.1~esm1
ubuntu/groovy<2.0.0~beta2+isreally1.8.6-4ubuntu1+esm1
2.0.0~beta2+isreally1.8.6-4ubuntu1+esm1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/groovy2 to a version that resolves this vulnerability.

    Fixed in 2.4.5-1ubuntu0.1~esm1
  2. Upgrade

    Upgrade ubuntu/groovy to a version that resolves this vulnerability.

    Fixed in 2.0.0~beta2+isreally1.8.6-4ubuntu1+esm1

Event History

Jan 18, 2018
CVE Published
via OSV·06:29 PM
Data Sourced
via OSV·06:29 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications with the affected Groovy versions on their classpath are exposed when they use standard Java serialization to exchange data between servers or store local data and do not isolate the code that deserializes objects.

2

What does an attacker need to exploit it?

An attacker needs a way to supply a specially crafted serialized object to an affected application so that the application deserializes it. No authentication or user interaction is required according to the supplied severity vector.

3

Are applications that include Groovy but do not deserialize objects affected?

The described attack requires use of standard Java serialization and deserialization of attacker-crafted objects. The provided information does not identify exposure for applications that do not perform this deserialization.

4

What can be done if the affected Groovy package cannot be updated immediately?

Avoid deserializing untrusted serialized objects, and isolate the code that performs deserialization. The description identifies applications that do not isolate deserialization code as subject to the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203