Skip to content
Fencer Intel
medium 5.1

CVE-2012-4424 json

Stack-based buffer overflow in string/strcoll_l.c in the GNU C Library (aka glibc or libc6) 2.17 and earlier allows context-dependent attac…

published 2013-10-09 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-4359

cvss
5.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.4%
EPSS 3.4% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

Stack-based buffer overflow in string/strcoll_l.c in the GNU C Library (aka glibc or libc6) 2.17 and earlier allows context-dependent attackers to cause a denial of service (crash) or possibly execute arbitrary code via a long string that triggers a malloc failure and use of the alloca function.

Patch / fix

  • glibc Debian 14, Debian 13, Debian 12 2.17-94

debian advisories DEBIAN-CVE-2012-4424

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-4424 updated cvss 3.7

glibc: alloca() stack overflow in the strcoll() interface

  • Red Hat Enterprise Linux 5 glibc Red Hat Enterprise Linux 6 nscd, glibc, glibc-utils, glibc-common
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 nscd, glibc, glibc-utils, glibc-common
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.38% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • sourceware.org http://sourceware.org/bugzilla/show_bug.cgi?id=14547 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.1 AV:N/AC:H/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.