Bug 1303887 - socat: Stack overflow vulnerability in parser
Summary: socat: Stack overflow vulnerability in parser
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1186301 1303888 1303889
Blocks: 1303890
TreeView+ depends on / blocked
 
Reported: 2016-02-02 10:52 UTC by Adam Mariš
Modified: 2021-02-17 04:23 UTC (History)
10 users (show)

Fixed In Version: socat 2.0.0-b9, socat 1.7.3.1
Clone Of:
Environment:
Last Closed: 2016-02-11 09:29:00 UTC
Embargoed:

Attachments (Terms of Use)

Description Adam Mariš 2016-02-02 10:52:46 UTC 
A stack overflow vulnerability was found that can be triggered when command line arguments (complete address specifications, host names, file names) are longer than 512 bytes. Successful exploitation might allow an attacker to execute arbitrary code with the privileges of the socat process. This vulnerability can only be exploited when an attacker is able to inject data into socat's command line. A vulnerable scenario would be a CGI script that reads data from clients and uses (parts of) this data as hostname for a Socat invocation.

Affected versions:
1.5.0.0 - 1.7.3.0
2.0.0-b1 - 2.0.0-b8

Reference:

http://seclists.org/oss-sec/2016/q1/262
Comment 1 Adam Mariš 2016-02-02 10:53:19 UTC 
Created socat tracking bugs for this issue:

Affects: fedora-all [bug 1303888]
Affects: epel-all [bug 1303889]
Comment 2 Tomas Hoger 2016-02-11 08:53:10 UTC 
Upstream commit:

http://repo.or.cz/socat.git/commitdiff/226c555edb82f6901d7d7448d93e6d09b1132c73

External References:

http://www.dest-unreach.org/socat/contrib/socat-secadv8.html
Comment 4 Tomas Hoger 2016-02-11 09:29:00 UTC 
Overflow is triggered by long command line arguments.  While these may be based on untrusted input, they typically are not.  There's currently no plan to correct this in Red Hat Enterprise Linux.  The fix may be added if the component is updated to fixed upstream version in future updates.
Note You need to log in before you can comment on or make changes to this bug.