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

> A buffer overflow in the SUSE blinux utility allows attackers to potentially execute arbitrary code or cause a crash via crafted input.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 18 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wfpj-872h-h97h

## What is CVE-2009-0310?

CVE-2009-0310 is a high-severity memory corruption vulnerability in Opensuse Opensuse, published on 18 Feb 2009. 

### Official description

Buffer overflow in SUSE blinux (aka sbl) in SUSE openSUSE 10.3 through 11.0 has unknown impact and attack vectors related to "incoming data and authentication-strings."

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

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

It affects 1 product.


Products: Opensuse Opensuse.

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

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

## Is CVE-2009-0310 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2015-5957](https://insights.sbomify.com/CVE-2015-5957/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-0491](https://insights.sbomify.com/CVE-2015-0491/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2388](https://insights.sbomify.com/CVE-2008-2388/): Integer overflow in n/a (critical 10.0)
- [CVE-2010-1866](https://insights.sbomify.com/CVE-2010-1866/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-0492](https://insights.sbomify.com/CVE-2015-0492/): Other in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0310 is a high-severity memory corruption vulnerability in Opensuse Opensuse, published on 18 Feb 2009. 
Exploitation: There is no known exploitation of CVE-2009-0310 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-0310/ (Markdown: https://insights.sbomify.com/CVE-2009-0310/index.md)
```

## Sources

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

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