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 standar
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.
- Published
- Jan 18, 2018
- Updated
- Jun 16, 2026
- EPSS
- 17.2% · 97th percentile
- CWE
- CWE-502
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
44
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 17.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| apache | groovy | cpe:2.3:a:apache:groovy |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache groovy1.7.0 and later · up to 2.4.3 inclusive
- apache groovy2.4.4 and later · up to 2.4.7 inclusive
- redhat enterprise linux server7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | groovy | before 2.4.8-1 | 2.4.8-1 |
| Debian:7 | groovy | before 1.8.6-1+deb7u2 | 1.8.6-1+deb7u2 |
| Maven | org.codehaus.groovy:groovy | from 1.7.0 · before 2.4.8 | 2.4.8 |
| Maven | org.codehaus.groovy:groovy-all | from 1.7.0 · before 2.4.8 | 2.4.8 |
| Red Hat:enterprise_linux:7::client | groovy | before 0:1.8.9-8.el7_4 | 0:1.8.9-8.el7_4 |
| Red Hat:enterprise_linux:7::client | groovy-javadoc | before 0:1.8.9-8.el7_4 | 0:1.8.9-8.el7_4 |
| Red Hat:rhel_software_collections:2::el6 | rh-maven33-groovy | before 0:1.8.9-7.19.el6 | 0:1.8.9-7.19.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-maven33-groovy-javadoc | before 0:1.8.9-7.19.el6 | 0:1.8.9-7.19.el6 |
| Red Hat:rhel_software_collections:2::el7 | rh-maven33-groovy | before 0:1.8.9-7.19.el7 | 0:1.8.9-7.19.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-maven33-groovy-javadoc | before 0:1.8.9-7.19.el7 | 0:1.8.9-7.19.el7 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-3253The MethodClosure class in runtime/MethodClosure.java in Apache Groovy 1.7.0 through 2.4.3 allows remote attackers to execute arbitrary code51Plan
- CVE-2020-17521Apache Groovy provides extension methods to aid with creating temporary directories.22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:groovy | 2.4.8-1 · Debian:12 | Package registry (OSV) |
| Maven:org.codehaus.groovy:groovy | 2.4.8 | Package registry (OSV) |
| Maven:org.codehaus.groovy:groovy-all | 2.4.8 | Package registry (OSV) |
| red hat:groovy | 0:1.8.9-8.el7_4 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:groovy-javadoc | 0:1.8.9-8.el7_4 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rh-maven33-groovy | 0:1.8.9-7.19.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-maven33-groovy-javadoc | 0:1.8.9-7.19.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)job = pickle.loads(payload)Fixed
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig): raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- mail-archives.apache.org/mod_mbox/www-announce/201701.mbox/%3CCADRx3PMZ2hBCGDTY35zYXFGaDnjAs0tc5-upaVs6QN2sYUejyA%40mail.gmail.com%3E
- rhn.redhat.com/errata/RHSA-2017-0272.html
- www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
- www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
- www.securityfocus.com/bid/95429
- www.securitytracker.com/id/1039600
- access.redhat.com/errata/RHSA-2017:0868
- access.redhat.com/errata/RHSA-2017:2486
- access.redhat.com/errata/RHSA-2017:2596
- security.gentoo.org/glsa/202003-01
- www.oracle.com/security-alerts/cpujan2020.html
- www.oracle.com/security-alerts/cpujul2020.html
- www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html
- www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
- www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.