# CVE-2009-2707: Denial of service in n/a

> Local users can crash the system via a 32-bit x86 application on SUSE Linux Enterprise Itanium systems.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q4h5-29hc-m9pq

## What is CVE-2009-2707?

CVE-2009-2707 is a medium-severity denial of service vulnerability in Novell Suse Linux Enterprise Server, published on 18 Sep 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in ia32el (aka the IA 32 emulation functionality) before 7042_7022-0.4.2 in SUSE Linux Enterprise (SLE) 10 SP2 on Itanium IA64 machines allows local users to cause a denial of service (system crash) via a 32-bit x86 application.

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

It affects 1 product.


Products: Novell Suse Linux Enterprise Server.

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

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

## Is CVE-2009-2707 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2707 is a medium-severity denial of service vulnerability in Novell Suse Linux Enterprise Server, published on 18 Sep 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-2707 in the wild and no public exploit code.

Affected product: Novell Suse Linux Enterprise Server. 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-2707/ (Markdown: https://insights.sbomify.com/CVE-2009-2707/index.md)
```

## Sources

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

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