CVE-2006-1902 json
fold_binary in fold-const.c in GNU Compiler Collection (gcc) 4.1 improperly handles pointer overflow when folding a certain expr comparison…
published 2006-04-20 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1902
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
fold_binary in fold-const.c in GNU Compiler Collection (gcc) 4.1 improperly handles pointer overflow when folding a certain expr comparison to a corresponding offset comparison in cases other than EQ_EXPR and NE_EXPR, which might introduce buffer overflow vulnerabilities into applications that could be exploited by context-dependent attackers.NOTE: the vendor states that the essence of the issue is "not correctly interpreting an offset to a pointer as a signed value."
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
securityfocus.com
/archive/1/431297/100/0/threaded
mailing-list
- gcc.gnu.org /bugzilla/show_bug.cgi?id=26763
-
securityfocus.com
/archive/1/431245/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/431319/100/0/threaded
mailing-list
- bugs.debian.org /cgi-bin/bugreport.cgi?bug=356896
-
securityfocus.com
/archive/1/431184/100/0/threaded
mailing-list
-
gcc.gnu.org
/ml/gcc-bugs/2006-04/msg01297.html
mailing-list
- gcc.gnu.org /viewcvs/branches/gcc-4_1-branch/gcc/fold-const.c?r1=110549&r2=112698&pathrev=112698&diff_format=h
-
gcc.gnu.org
/ml/gcc-bugs/2006-04/msg01298.html
mailing-list
Sources
- CVE List CVE-2006-1902
- NVD CVE-2006-1902
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.