CVE-2016-6814Not scoredCWE-502

CVE-2016-6814: Apache Groovy vulnerability

Apache · Groovy

Vendor fix available · Affected: Apache Groovy · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

17.2%probability of exploitation in the next 30 days

97th percentile

050100

Higher than 97% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Deserialization of Untrusted Data · Deserialization and Object Injection
Vendor: Apache
Published: January 2018
Band: Likely to be exploited (10% or more), January 2018

CoverageNo articles yet

No CyberSIXT article names CVE-2016-6814 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

4 more references are in the CVE record.