# CVE-2002-2439: Integer overflow in the new[] operator in gcc before 4.8.0 allows attackers to have unspecified impacts.


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2019
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mm8j-7g3h-x2mj, UBUNTU-CVE-2002-2439

## What is CVE-2002-2439?

CVE-2002-2439 is a high-severity vulnerability in GNU gcc, published on 23 Oct 2019. 

### Official description

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

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2002-2439?

It affects 1 product.


Products: Gnu Gcc.

## How do I fix CVE-2002-2439?

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

## Is CVE-2002-2439 being exploited?

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

## Other vulnerabilities in GNU gcc

- [CVE-2018-12886](https://insights.sbomify.com/CVE-2018-12886/): Security feature bypass in n/a (high 8.1)
- [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)
- [CVE-2021-46195](https://insights.sbomify.com/CVE-2021-46195/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2439 and fix it if it is affected.

What it is: CVE-2002-2439 is a high-severity vulnerability in GNU gcc, published on 23 Oct 2019. 
Exploitation: There is no known exploitation of CVE-2002-2439 in the wild and no public exploit code.

Affected product: GNU gcc. 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-2002-2439/ (Markdown: https://insights.sbomify.com/CVE-2002-2439/index.md)
```

## Sources

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

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