CVE-2010-2799: Buffer Overflow
Socat upstream, released an advisory: [1] http://www.dest-unreach.org/socat/contrib/socat-secadv2.html
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] http://bugs.gentoo.org/showbug.cgi?id=330785
Upstream patch against v1.7.2: [3] http://www.dest-unreach.org/socat/download/socat-1.7.1.3.patch
Credit: Issue discovered and reported by Felix Gröbert of Google Security Team
CVE Request: [4] http://www.openwall.com/lists/oss-security/2010/08/02/3
Other sources
Stack-based buffer overflow in the nestlex function in nestlex.c in Socat 1.5.0.0 through 1.7.1.2 and 2.0.0-b1 through 2.0.0-b3, when bidirectional data relay is enabled, allows context-dependent attackers to execute arbitrary code via long command-line arguments.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2010-2799?
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.
How do I fix CVE-2010-2799?
To fix CVE-2010-2799, upgrade to the latest version of Socat that addresses this vulnerability.
What versions of Socat are affected by CVE-2010-2799?
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.
What are the potential impacts of CVE-2010-2799?
Exploitation of CVE-2010-2799 could allow an attacker to execute arbitrary code, potentially compromising the affected system.
Is there a workaround for CVE-2010-2799?
There are no known workarounds for CVE-2010-2799; the recommended action is to update Socat to a secure version.