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

> A stack-based buffer overflow in Winplot allows remote attackers to execute arbitrary code by tricking users into opening a malicious .wp2 file.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g5jm-7h4m-pp3x

## What is CVE-2009-3329?

CVE-2009-3329 is a critical memory corruption vulnerability in n/a, published on 23 Sep 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in Winplot 1.25.0.1 allows user-assisted remote attackers to execute arbitrary code via a crafted Plot2D (.wp2) file.

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

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

It affects 1 product.


Products: Exeter Winplot.

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

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

## Is CVE-2009-3329 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3329 is a critical memory corruption vulnerability in n/a, published on 23 Sep 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-3329 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-2009-3329/ (Markdown: https://insights.sbomify.com/CVE-2009-3329/index.md)
```

## Sources

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

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