First published: Mon Aug 02 2010(Updated: )
Socat upstream, released an advisory: [1] <a href="http://www.dest-unreach.org/socat/contrib/socat-secadv2.html">http://www.dest-unreach.org/socat/contrib/socat-secadv2.html</a> describing a stack overflow flaw, present in Socat bidirectional data relay, when processing command line arguments (address specifications, host names, file names), longer than 512 bytes. An attacker, able to inject data into sockat's command line (potentially remotely via CGI script invocation), could use this flaw to execute arbitrary code with the privileges of the socat process. References: [2] <a href="http://bugs.gentoo.org/show_bug.cgi?id=330785">http://bugs.gentoo.org/show_bug.cgi?id=330785</a> Upstream patch against v1.7.2: [3] <a href="http://www.dest-unreach.org/socat/download/socat-1.7.1.3.patch">http://www.dest-unreach.org/socat/download/socat-1.7.1.3.patch</a> Credit: Issue discovered and reported by Felix Gröbert of Google Security Team CVE Request: [4] <a href="http://www.openwall.com/lists/oss-security/2010/08/02/3">http://www.openwall.com/lists/oss-security/2010/08/02/3</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
socat | =1.7.1.1 | |
socat | =1.7.0.0 | |
socat | =1.5.0.0 | |
socat | =2.0.0-b3 | |
socat | =1.6.0.0 | |
socat | =1.7.1.0 | |
socat | =2.0.0-b2 | |
socat | =1.6.0.1 | |
socat | =2.0.0-b1 | |
socat | =1.7.0.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-2799 has been classified as a critical vulnerability due to its potential for a stack overflow which could lead to remote code execution.
To fix CVE-2010-2799, upgrade to the latest version of Socat that addresses this vulnerability.
CVE-2010-2799 affects multiple versions of Socat including 1.5.0.0 through 1.7.1.1 and 2.0.0-b1 through 2.0.0-b3.
Exploitation of CVE-2010-2799 could allow an attacker to execute arbitrary code, potentially compromising the affected system.
There are no known workarounds for CVE-2010-2799; the recommended action is to update Socat to a secure version.