socat contains a format string vulnerability that can potentially lead to remote or local execution of arbitrary code with the privileges of the socat process.
|Package||net-misc/socat on all architectures|
|Affected versions||< 220.127.116.11|
|Unaffected versions||>= 18.104.22.168|
socat is a multipurpose bidirectional relay, similar to netcat.
socat contains a syslog() based format string vulnerablility in the '_msg()' function of 'error.c'. Exploitation of this bug is only possible when socat is run with the '-ly' option, causing it to log messages to syslog.
Remote exploitation is possible when socat is used as a HTTP proxy client and connects to a malicious server. Local privilege escalation can be achieved when socat listens on a UNIX domain socket. Potential execution of arbitrary code with the privileges of the socat process is possible with both local and remote exploitations.
Disable logging to syslog by not using the '-ly' option when starting socat.
All socat users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=net-misc/socat-22.214.171.124"
October 25, 2004
May 22, 2006: 02