From red hat bugzilla: Multiple integer overflows, leading to stack-based buffer overflows were found in various stdlib functions of GNU libc (strtod, strtof, strtold, strtod_l and related routines). If an application, using the affected stdlib functions, did not perform user-level sanitization of provided inputs, a local attacker could use this flaw to cause such an application to crash or, potentially, execute arbitrary code with the privileges of the user running the application. Upstream bug report: [1] http://sourceware.org/bugzilla/show_bug.cgi?id=14459 Upstream patch (might not be the final one): [2] http://sourceware.org/ml/libc-alpha/2012-08/msg00202.html
Add upstream because it may not be the final patch
CVE-2012-3480 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-3480): Multiple integer overflows in the (1) strtod, (2) strtof, (3) strtold, (4) strtod_l, and other unspecified "related functions" in stdlib in GNU C Library (aka glibc or libc6) 2.16 allow local users to cause a denial of service (application crash) and possibly execute arbitrary code via a long string, which triggers a stack-based buffer overflow.
Upstream bug listed in c0 contains backport commit id's for 2.15 and 2.16 as well as a commit for 2.17.
yes, but i won't be doing that. i doubt they'll make another 2.15 release, and i'm not sure there will be a 2.16.1. which makes 2.17 the next target.
@maintainers: Unless 2.17 will be stabled with a fix soon, need to patch and stable 2.15.
glibc-2.17 is in stable now
Maintainer(s), please drop the vulnerable version. New GLSA Request filed.
Added to existing GLSA request.
This issue was resolved and addressed in GLSA 201503-04 at http://security.gentoo.org/glsa/glsa-201503-04.xml by GLSA coordinator Kristian Fiskerstrand (K_F).