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

> Remote attackers can execute arbitrary code by tricking users into opening a malicious .WRL file in White_Dune.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0100, GHSA-2v3w-6hfw-3w66

## What is CVE-2008-0100?

CVE-2008-0100 is a high-severity memory corruption vulnerability in n/a, published on 8 Jan 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in the Scene::errorf function in Scene.cpp in White_Dune 0.29 beta791 and earlier allows remote attackers to execute arbitrary code via a long string in a .WRL file.

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

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

It affects 1 product.


Products: White Dune White Dune.

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

Upgrade to a fixed version.

## Is CVE-2008-0100 being exploited?

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

Public exploit code:

- White_Dune 0.29beta791 - Multiple Local Code Execution Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-7228](https://insights.sbomify.com/CVE-2008-7228/): Other in n/a (critical 10.0)
- [CVE-2008-0101](https://insights.sbomify.com/CVE-2008-0101/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0100 is a high-severity memory corruption vulnerability in n/a, published on 8 Jan 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0100 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-2008-0100/ (Markdown: https://insights.sbomify.com/CVE-2008-0100/index.md)
```

## Sources

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

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