# CVE-2006-1990: Integer overflow in n/a

> Integer overflow in PHP's wordwrap function allows remote attackers to execute arbitrary code via long arguments causing heap-based buffer overflow.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 24 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jpv3-m3h3-ph93

## What is CVE-2006-1990?

CVE-2006-1990 is a medium-severity vulnerability in Php Php, published on 24 Apr 2006. It can be exploited over the network.

### Official description

Integer overflow in the wordwrap function in string.c in PHP 4.4.2 and 5.1.2 might allow context-dependent attackers to execute arbitrary code via certain long arguments that cause a small buffer to be allocated, which triggers a heap-based buffer overflow in a memcpy function call, a different vulnerability than CVE-2002-1396.

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2006-1990 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1990 is a medium-severity vulnerability in Php Php, published on 24 Apr 2006. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-1990 in the wild and no public exploit code.

Affected product: Php Php. 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-1990/ (Markdown: https://insights.sbomify.com/CVE-2006-1990/index.md)
```

## Sources

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

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