CVE-2014-0019: Buffer Overflow
First published: Tue Feb 04 2014(Updated: )
Stack-based buffer overflow in socat 1.3.0.0 through 1.7.2.2 and 2.0.0-b1 through 2.0.0-b6 allows local users to cause a denial of service (segmentation fault) via a long server name in the PROXY-CONNECT address in the command line.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| socat | =2.0.0-b1 | |
| socat | =2.0.0-b2 | |
| socat | =2.0.0-b3 | |
| socat | =2.0.0-b4 | |
| socat | =2.0.0-b5 | |
| socat | =2.0.0-b6 | |
| Fedora | =19 | |
| Fedora | =20 | |
| SUSE Linux | =13.1 | |
| socat | =1.3.0.0 | |
| socat | =1.3.0.1 | |
| socat | =1.3.1.0 | |
| socat | =1.3.2.0 | |
| socat | =1.3.2.1 | |
| socat | =1.3.2.2 | |
| socat | =1.4.0.0 | |
| socat | =1.4.0.1 | |
| socat | =1.4.0.2 | |
| socat | =1.4.0.3 | |
| socat | =1.4.1.0 | |
| socat | =1.4.2.0 | |
| socat | =1.4.3.0 | |
| socat | =1.4.3.1 | |
| socat | =1.5.0.0 | |
| socat | =1.6.0.0 | |
| socat | =1.6.0.1 | |
| socat | =1.7.0.0 | |
| socat | =1.7.0.1 | |
| socat | =1.7.1.0 | |
| socat | =1.7.1.1 | |
| socat | =1.7.1.2 | |
| socat | =1.7.1.3 | |
| socat | =1.7.2.0 | |
| socat | =1.7.2.1 | |
| socat | =1.7.2.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://lists.fedoraproject.org/pipermail/package-announce/2014-February/128190.html
- http://lists.fedoraproject.org/pipermail/package-announce/2014-February/128229.html
- http://lists.opensuse.org/opensuse-updates/2015-04/msg00043.html
- http://osvdb.org/102612
- http://seclists.org/oss-sec/2014/q1/159
- http://www.dest-unreach.org/socat
- http://www.dest-unreach.org/socat/contrib/socat-secadv5.txt
- http://www.mandriva.com/security/advisories?name=MDVSA-2014:033
- http://www.securityfocus.com/bid/65201
Frequently Asked Questions
What is the severity of CVE-2014-0019?
CVE-2014-0019 has a medium severity rating due to its potential to cause denial of service through segmentation faults.
How do I fix CVE-2014-0019?
To fix CVE-2014-0019, update socat to versions 2.0.0-b7 or later, or apply vendor patches available for earlier versions.
Which versions of socat are affected by CVE-2014-0019?
CVE-2014-0019 affects socat versions from 1.3.0.0 through 1.7.2.2 as well as certain 2.0.0-Beta versions.
What could happen if CVE-2014-0019 is exploited?
If exploited, CVE-2014-0019 can lead to a denial of service condition by causing the application to crash.
Who should be concerned about CVE-2014-0019?
Users and administrators running affected versions of socat should be concerned and take immediate action to mitigate the vulnerability.
- agent/type
- agent/remedy
- agent/references
- agent/author
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/weakness
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/dest-unreach
- canonical/socat
- version/socat/2.0.0-b1
- version/socat/2.0.0-b2
- version/socat/2.0.0-b3
- version/socat/2.0.0-b4
- version/socat/2.0.0-b5
- version/socat/2.0.0-b6
- vendor/fedoraproject
- canonical/fedora
- version/fedora/19
- version/fedora/20
- vendor/opensuse
- canonical/suse linux
- version/suse linux/13.1
- version/socat/1.3.0.0
- version/socat/1.3.0.1
- version/socat/1.3.1.0
- version/socat/1.3.2.0
- version/socat/1.3.2.1
- version/socat/1.3.2.2
- version/socat/1.4.0.0
- version/socat/1.4.0.1
- version/socat/1.4.0.2
- version/socat/1.4.0.3
- version/socat/1.4.1.0
- version/socat/1.4.2.0
- version/socat/1.4.3.0
- version/socat/1.4.3.1
- version/socat/1.5.0.0
- version/socat/1.6.0.0
- version/socat/1.6.0.1
- version/socat/1.7.0.0
- version/socat/1.7.0.1
- version/socat/1.7.1.0
- version/socat/1.7.1.1
- version/socat/1.7.1.2
- version/socat/1.7.1.3
- version/socat/1.7.2.0
- version/socat/1.7.2.1
- version/socat/1.7.2.2