Skip to content
Fencer Intel
medium 4.4

CVE-2012-5667 json

Multiple integer overflows in GNU Grep before 2.11 might allow context-dependent attackers to execute arbitrary code via vectors involving…

published 2013-01-03 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5550

cvss
4.4
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
1
Exploit-DB

Summary

Multiple integer overflows in GNU Grep before 2.11 might allow context-dependent attackers to execute arbitrary code via vectors involving a long input line that triggers a heap-based buffer overflow.

Patch / fix

  • grep Debian 14, Debian 13, Debian 12 2.11-1

debian advisories DEBIAN-CVE-2012-5667

  • grep RHEL 6 2.20-3.el6

red hat advisories RHSA-2015:1447

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-5667 updated cvss 4.4

grep: Integer overflow leading to heap-based buffer-overflow when reading large lines

  • Red Hat Enterprise Linux Desktop (v. 6) grep 2.20-3.el6 Red Hat Enterprise Linux HPC Node (v. 6) grep 2.20-3.el6 Red Hat Enterprise Linux Server (v. 6) grep 2.20-3.el6 Red Hat Enterprise Linux Workstation (v. 6) grep 2.20-3.el6
    fixed: vendor fix RHSA-2015:1447
  • Red Hat Enterprise Linux 5 grep Red Hat Enterprise Linux 7 grep
    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

Timeline

  1. First public exploit (EDB-23779)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-23779 Grep < 2.11 - Integer Overflow Crash (PoC) dos, 2012-12-31

CVSS scores

assigned by version score vector
NVD 2.0 4.4 AV:L/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

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.