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

> Remote attackers can execute arbitrary commands or crash the system via a buffer overflow in the MLF application of AREVA e-terrahabitat.

- **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 needed
- **Fix available:** No
- **Published:** 8 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7m94-2cc2-pg52

## What is CVE-2009-0210?

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

### Official description

Buffer overflow in the MLF application in AREVA e-terrahabitat 5.7 and earlier allows remote attackers to execute arbitrary commands or cause a denial of service (system crash) via unspecified vectors, aka PD28578.

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

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

It affects 1 product.


Products: Areva E-Terrahabitat.

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

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

## Is CVE-2009-0210 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0214](https://insights.sbomify.com/CVE-2009-0214/): Privilege escalation in n/a (critical 9.0)
- [CVE-2009-0211](https://insights.sbomify.com/CVE-2009-0211/): Denial of service in n/a (high 7.8)
- [CVE-2009-0212](https://insights.sbomify.com/CVE-2009-0212/): Denial of service in n/a (high 7.8)
- [CVE-2009-0213](https://insights.sbomify.com/CVE-2009-0213/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0210 is a critical memory corruption vulnerability in n/a, published on 8 Feb 2009. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-0210 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-0210/ (Markdown: https://insights.sbomify.com/CVE-2009-0210/index.md)
```

## Sources

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

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