FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-04-18 11:12:36 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML ID	Description
4af92a40-db33-11e6-ae1b-002590263bf5	groovy -- remote execution of untrusted code/DoS vulnerability The Apache Groovy project reports: When an application with Groovy on classpath uses standard Java serialization mechanisms, e.g. to communicate between servers or to store local data, it is 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 are subject to this vulnerability. This is similar to CVE-2015-3253 but this exploit involves extra wrapping of objects and catching of exceptions which are now safe guarded against. Discovery 2016-09-20 Entry 2017-01-15 groovy ge 1.7.0 lt 2.4.8 CVE-2016-6814 http://groovy-lang.org/security.html
67b3fef2-2bea-11e5-86ff-14dae9d210b8	groovy -- remote execution of untrusted code CÃ©dric Champeau reports: Description When an application has Groovy on the classpath and that it uses standard Java serialization mechanism to communicate between servers, or to store local data, it is 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 are subject to this vulnerability. Discovery 2015-07-09 Entry 2015-07-16 groovy ge 1.7.0 lt 2.4.4 http://seclists.org/oss-sec/2015/q3/121 http://groovy-lang.org/security.html https://issues.apache.org/jira/browse/GROOVY-7504 CVE-2015-3253

VuXML ID

Description

4af92a40-db33-11e6-ae1b-002590263bf5

groovy -- remote execution of untrusted code/DoS vulnerability

The Apache Groovy project reports:

When an application with Groovy on classpath uses standard Java serialization mechanisms, e.g. to communicate between servers or to store local data, it is 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 are subject to this vulnerability. This is similar to CVE-2015-3253 but this exploit involves extra wrapping of objects and catching of exceptions which are now safe guarded against.

Discovery 2016-09-20
Entry 2017-01-15
groovy

ge 1.7.0 lt 2.4.8

CVE-2016-6814
http://groovy-lang.org/security.html

67b3fef2-2bea-11e5-86ff-14dae9d210b8

groovy -- remote execution of untrusted code

Description

When an application has Groovy on the classpath and that it uses standard Java serialization mechanism to communicate between servers, or to store local data, it is 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 are subject to this vulnerability.

Discovery 2015-07-09
Entry 2015-07-16
groovy

ge 1.7.0 lt 2.4.4

http://seclists.org/oss-sec/2015/q3/121
http://groovy-lang.org/security.html
https://issues.apache.org/jira/browse/GROOVY-7504
CVE-2015-3253