# CVE-2009-0659: Memory corruption in n/a

> Remote attackers can trigger a stack-based buffer overflow in TPTEST via a crafted STATS line, potentially causing code execution or crashes.

- **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 needed
- **Fix available:** No
- **Published:** 20 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2586-6m27-6w97

## What is CVE-2009-0659?

CVE-2009-0659 is a medium-severity memory corruption vulnerability in n/a, published on 20 Feb 2009. It can be exploited over the network, with no action from the victim.

### Official description

Stack-based buffer overflow in the GetStatsFromLine function in TPTEST 3.1.7 allows remote attackers to have an unknown impact via a STATS line with a long email field.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

## Which versions are affected by CVE-2009-0659?

It affects 1 product.


Products: Tptest Tptest.

## How do I fix CVE-2009-0659?

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

## Is CVE-2009-0659 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0659 exists.

Public exploit code:

- TPTEST 3.1.7 - Stack Buffer Overflow (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-0650](https://insights.sbomify.com/CVE-2009-0650/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0659 and fix it if it is affected.

What it is: CVE-2009-0659 is a medium-severity memory corruption vulnerability in n/a, published on 20 Feb 2009. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0659 exists.

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-2009-0659/ (Markdown: https://insights.sbomify.com/CVE-2009-0659/index.md)
```

## Sources

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

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