Skip to content
Fencer Intel
medium 6.2

CVE-2011-5320 json

scanf and related functions in glibc before 2.15 allow local users to cause a denial of service (segmentation fault) via a large string of…

published 2017-10-18 9 y ago modified 2026-06-16 4 mo ago also EUVD-2011-5219

cvss
6.2
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

scanf and related functions in glibc before 2.15 allow local users to cause a denial of service (segmentation fault) via a large string of 0s.

Patch / fix

  • glibc Debian 14, Debian 13, Debian 12 2.15

debian advisories DEBIAN-CVE-2011-5320

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-2011-5320 updated cvss 1.9

glibc: scanf implementation crashes on certain inputs

  • 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

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

Exploits and checks

  • marc.info https://marc.info/?l=gimp-developer&m=129567990905823&w=2 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 6.2 CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/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.