# CVE-2006-7207: Memory corruption in n/a

> Remote attackers may exploit a buffer overflow in AGEphone to cause denial of service or execute arbitrary code.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 22 Jun 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4v42-r9rw-39fj

## What is CVE-2006-7207?

CVE-2006-7207 is a critical memory corruption vulnerability in n/a, published on 22 Jun 2007. It can be exploited over the network.

### Official description

Buffer overflow in ageet AGEphone before 1.4.0 might allow remote attackers to have an unknown impact via unspecified vectors.

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

It affects 1 product.


Products: Ageet Agephone.

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

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

## Is CVE-2006-7207 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3363](https://insights.sbomify.com/CVE-2007-3363/): Other in n/a (critical 10.0)
- [CVE-2007-3362](https://insights.sbomify.com/CVE-2007-3362/): Denial of service in n/a (high 7.8)
- [CVE-2006-4029](https://insights.sbomify.com/CVE-2006-4029/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-7207 is a critical memory corruption vulnerability in n/a, published on 22 Jun 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-7207 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-7207/ (Markdown: https://insights.sbomify.com/CVE-2006-7207/index.md)
```

## Sources

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

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