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

> Local attackers can cause a denial of service via a stack-based buffer overflow in openMosix tools, though no known exploit exists.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-92r4-4px6-qvvf

## What is CVE-2008-1865?

CVE-2008-1865 is a low-severity memory corruption vulnerability in n/a, published on 17 Apr 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based buffer overflow in the msx_readnode function in libmosix.c in openmosix-tools (aka userspace-tools) in openMosix might allow local users to cause a denial of service (application crash) via a third-party program that calls this function with a long item argument.  NOTE: the vendor does not provide any program that is capable of causing this overflow.

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

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

It affects 1 product.


Products: Openmosix Project Openmosix.

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

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

## Is CVE-2008-1865 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1865 is a low-severity memory corruption vulnerability in n/a, published on 17 Apr 2008. 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-2008-1865 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-1865/ (Markdown: https://insights.sbomify.com/CVE-2008-1865/index.md)
```

## Sources

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

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