socat: Format string vulnerability
1.
Gentoo Linux Security Advisory
Version Information
| Advisory Reference |
GLSA 200410-26 / socat |
| Release Date |
October 25, 2004 |
| Latest Revision |
May 22, 2006: 02 |
| Impact |
normal |
| Exploitable |
remote |
| Package |
Vulnerable versions |
Unaffected versions |
Architecture(s) |
| net-misc/socat |
<
1.4.0.3 |
>=
1.4.0.3 |
All supported architectures
|
Related bugreports:
#68547
Synopsis
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.
2.
Impact Information
Background
socat is a multipurpose bidirectional relay, similar to netcat.
Description
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.
Impact
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.
3.
Resolution Information
Workaround
Disable logging to syslog by not using the '-ly' option when starting
socat.
Resolution
All socat users should upgrade to the latest version:
Code Listing 3.1: Resolution |
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-misc/socat-1.4.0.3"
|
4.
References
|