# CVE-2008-3908: Memory corruption in n/a

> Buffer overflows in WordNet allow arbitrary code execution via malicious arguments or environment variables, impacting applications using the library.

- **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 needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** AZL-37061, AZL-7423, DEBIAN-CVE-2008-3908, DTSA-163-1, GHSA-7rh6-v5xq-4587

## What is CVE-2008-3908?

CVE-2008-3908 is a critical memory corruption vulnerability in n/a, published on 4 Sep 2008. 

### Official description

Multiple buffer overflows in Princeton WordNet (wn) 3.0 allow context-dependent attackers to execute arbitrary code via (1) a long argument on the command line; a long (2) WNSEARCHDIR, (3) WNHOME, or (4) WNDBVERSION environment variable; or (5) a user-supplied dictionary (aka data file).  NOTE: since WordNet itself does not run with special privileges, this issue only crosses privilege boundaries when WordNet is invoked as a third party component.

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

## Which versions are affected by CVE-2008-3908?

It affects 1 product.


Products: Princeton University Wordnet.

## How do I fix CVE-2008-3908?

Upgrade to a fixed version.

## Is CVE-2008-3908 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3908 and fix it if it is affected.

What it is: CVE-2008-3908 is a critical memory corruption vulnerability in n/a, published on 4 Sep 2008. 
Exploitation: There is no known exploitation of CVE-2008-3908 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-2008-3908/ (Markdown: https://insights.sbomify.com/CVE-2008-3908/index.md)
```

## Sources

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

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