Apache Groovy deserialization flaws allow code execution
Original title: USN-9101-1: Apache Groovy vulnerabilities
CVE-2015-3253 and CVE-2016-6814 can yield arbitrary code execution; the first can also cause denial of service.
Ubuntu published USN-9101-1 covering two Apache Groovy issues. Incorrect handling of MethodClosure deserialization (CVE-2015-3253) could allow arbitrary code execution or denial of service. Incorrect serialization handling (CVE-2016-6814) could allow arbitrary code execution. The snippet does not state versions or known attacks.
Unconfirmed: The snippet does not state affected versions, fixes, or whether the flaws are exploited.
- CVE-2015-3253 concerns deserialization of MethodClosure objects.
- CVE-2016-6814 concerns Groovy serialization mechanisms.
- Both issues are described as possible arbitrary code execution paths.
Impact: arbitrary code execution or denial of service
| Product | Affected |
|---|---|
| Apache Groovy | — |
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2015-3253 | — | — | — | ||
| CVE-2016-6814 | 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… | 9.8 | 17% |
From the original article
It was discovered that Apache Groovy incorrectly handled the deserialization of MethodClosure objects. An attacker could possibly use this issue to execute arbitrary code or cause a denial of service. (CVE-2015-3253) It was discovered that Apache Groovy incorrectly handled serialization mechanisms.
ubuntu.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.