blob: 4d7ebf369f499fa2d1cfcc4c6e30aed682edc750 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200410-26">
<title>socat: Format string vulnerability</title>
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.
<product type="ebuild">socat</product>
<announced>October 25, 2004</announced>
<revised>May 22, 2006: 02</revised>
<package name="net-misc/socat" auto="yes" arch="*">
<unaffected range="ge"></unaffected>
<vulnerable range="lt"></vulnerable>
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.
<impact type="normal">
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
All socat users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=net-misc/socat-;</code>
<uri link="">socat Security Advisory</uri>
<uri link="">CVE-2004-1484</uri>
<metadata tag="requester" timestamp="Sat, 23 Oct 2004 13:12:08 +0000">
<metadata tag="bugReady" timestamp="Sat, 23 Oct 2004 13:30:23 +0000">
<metadata tag="submitter" timestamp="Sun, 24 Oct 2004 21:38:40 +0000">