First published: Mon Dec 03 2012(Updated: )
A format string flaw was reported [1] in libproxy's proxy commandline tool (bin/proxy). This was corrected upstream [2] and is included in the 0.4.0 release. FORTIFY_SOURCE turns this into a harmless crash: % http_proxy=<a href="http://foo%n.example.com/">http://foo%n.example.com/</a> proxy <a href="http://example.com">http://example.com</a> *** %n in writable segment detected *** <a href="http://foozsh">http://foozsh</a>: abort (core dumped) http_proxy=<a href="http://foo%n.example.com/">http://foo%n.example.com/</a> proxy <a href="http://example.com">http://example.com</a> NOTE: this flaw exists solely in the proxy tool, not the library. [1] <a href="https://bugzilla.novell.com/show_bug.cgi?id=791086">https://bugzilla.novell.com/show_bug.cgi?id=791086</a> [2] <a href="https://code.google.com/p/libproxy/source/detail?r=475">https://code.google.com/p/libproxy/source/detail?r=475</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/libproxy | <0.4.0 | 0.4.0 |
Oracle Libproxy | =0.3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-5580 has a moderate to high severity level due to the potential for a format string vulnerability.
To fix CVE-2012-5580, you should upgrade libproxy to version 0.4.0 or later.
CVE-2012-5580 affects libproxy version 0.3.1 and earlier versions.
No official workaround is recommended for CVE-2012-5580; upgrading is the best solution.
CVE-2012-5580 was reported by a security researcher and discussed in public vulnerability databases.