Skip to content
Fencer Vulns
high 7.8

CVE-2002-2439 json

Integer overflow in the new[] operator in gcc before 4.8.0 allows attackers to have unspecified impacts.

published 2019-10-23 7 y ago modified 2026-06-16 4 mo ago also EUVD-2002-2417

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

Summary

Integer overflow in the new[] operator in gcc before 4.8.0 allows attackers to have unspecified impacts.

Patch / fix

  • gnu gcc 4.8.0

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-2002-2439 updated cvss 3.7

gcc: Integer overflow can occur during the computation of the memory region size for new[] operator

  • Red Hat Enterprise Linux 5 gcc, gcc43, gcc44, compat-gcc-32, compat-gcc-34, compat-gcc-295, +1 more Red Hat Enterprise Linux 6 cpp, gcc, libgcc, libgcj, libitm, gcc-c++, +23 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 cpp, gcc, libgo, gcc-go, libgcc, libitm, +15 more
    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.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2002-2439 referenced PoC, tagged "exploit" by a source, unverified
  • gcc.gnu.org https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19351 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • GNU gcc

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Vulns 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.