Alerts This Week
Warning Icon 1 640
Alerts This Week
Warning Icon 1 640

Gentoo: GLSA-202003-01 Normal: Groovy Code Execution Risk

gentoo
Calendar Grey March 12, 2020
Dist Gentoo Esm H88
A recent security notice regarding Groovy for Gentoo highlights a moderate severity vulnerability that could lead to the execution of arbitrary code.
A vulnerability within serialization might allow remote attackers to execute arbitrary code.

Summary

It was discovered that there was a vulnerability within the Java serialization/deserialization process.

Resolution

Gentoo has discontinued support for Groovy. We recommend that usersunmerge Groovy: # emerge --unmerge "dev-java/groovy"

References

[ 1 ] CVE-2016-6814 https://nvd.nist.gov/vuln/detail/CVE-2016-6814

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202003-01
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: Groovy: Arbitrary code execution
Date: March 07, 2020
Bugs: #605690
ID: 202003-01

Synopsis

A vulnerability within serialization might allow remote attackers to execute arbitrary code.

Background

A multi-faceted language for the Java platform

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-java/groovy <= 2.4.5 Vulnerable! ------------------------------------------------------------------- NOTE: Certain packages are still vulnerable. Users should migrate to another package if one is available or wait for the existing packages to be marked stable by their architecture maintainers.

Impact

===== An attacker, by crafting a special serialized object, could execute arbitrary code.

Workaround

There is no known workaround at this time.

Your message here