# CVE-2006-1902: fold_binary in fold-const.c in GNU Compiler Collection (gcc) 4.1 improperly handles pointer overflow when folding a certain expr comparison


- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r8fv-8gwf-v44c

## What is CVE-2006-1902?

CVE-2006-1902 is a low-severity vulnerability in n/a, published on 20 Apr 2006. 

### Official description

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."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2006-1902?

It affects 1 product.


Products: Gnu Gcc.

## How do I fix CVE-2006-1902?

No fix has been published for CVE-2006-1902 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-1902 being exploited?

There is no known exploitation of CVE-2006-1902 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-12886](https://insights.sbomify.com/CVE-2018-12886/): Security feature bypass in n/a (high 8.1)
- [CVE-2002-2439](https://insights.sbomify.com/CVE-2002-2439/): Integer overflow in the new[] operator in gcc before 4.8.0 allows attackers to have unspecified impacts. (high 7.8)
- [CVE-2019-15847](https://insights.sbomify.com/CVE-2019-15847/): Weak cryptography in n/a (high 7.5)
- [CVE-2008-1367](https://insights.sbomify.com/CVE-2008-1367/): Memory corruption in n/a (high 7.5)
- [CVE-2008-1685](https://insights.sbomify.com/CVE-2008-1685/): Integer overflow in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1902 and fix it if it is affected.

What it is: CVE-2006-1902 is a low-severity vulnerability in n/a, published on 20 Apr 2006. 
Exploitation: There is no known exploitation of CVE-2006-1902 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-1902/ (Markdown: https://insights.sbomify.com/CVE-2006-1902/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-1902
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-1902
- OSV: https://osv.dev/vulnerability/CVE-2006-1902

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-1902/
Summaries are generated and may contain mistakes; the official description above is the record.