VYPR
Unrated severityNVD Advisory· Published Oct 9, 2013· Updated Apr 29, 2026

CVE-2012-4412

CVE-2012-4412

Description

Integer 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, which triggers a heap-based buffer overflow.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

An integer overflow in glibc's `strcoll_l()` function, versions 2.17 and earlier, allows a long string to trigger heap-based buffer overflow, leading to denial of service or arbitrary code execution.

Vulnerability

An integer overflow vulnerability exists in the strcoll_l function within string/strcoll_l.c of the GNU C Library (glibc) versions 2.17 and earlier [3]. When processing a long string, this overflow leads to a heap-based buffer overflow [3]. The vulnerability is context-dependent, meaning specific conditions are required for the overflow to be triggered [3].

Exploitation

An attacker can exploit this vulnerability by providing a long string to an application that uses the affected strcoll_l function for string collation [3]. The attacker does not need any special privileges; the attack is triggered by the input data itself [3]. The exact steps involve crafting a string that, when passed to strcoll_l, causes an integer overflow in size calculations, leading to a subsequent heap buffer write beyond allocated bounds [3].

Impact

Successful exploitation can result in a denial of service (application crash) or, potentially, arbitrary code execution [3]. The impact is context-dependent, as the attacker's control over the heap-based overflow may allow for code execution with the privileges of the vulnerable process [3].

Mitigation

Ubuntu released security update USN-1991-1 on October 21, 2013, which fixed this vulnerability in eglibc (the Debian/Ubuntu variant of glibc) [3]. Users should update to the fixed version provided by their distribution. No workarounds other than applying the patch are mentioned in the references. For glibc versions prior to 2.18, the fix is incorporated by updating to that release or later [3].

AI Insight generated on May 23, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

27
  • GNU/Glibc26 versions
    cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*+ 25 more
    • cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*range: <=2.17
    • cpe:2.3:a:gnu:glibc:2.0:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.0.1:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.0.2:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.0.3:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.0.4:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.0.5:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.0.6:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.1:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.10.1:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.1.1:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.11:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.11.1:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.11.2:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.11.3:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.1.1.6:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.1.2:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.12.1:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.12.2:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.1.3:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.13:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.14:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.14.1:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.15:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.16:*:*:*:*:*:*:*
    • cpe:2.3:a:gnu:glibc:2.1.9:*:*:*:*:*:*:*

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

11

News mentions

0

No linked articles in our index yet.