# CVE-2005-0385: Memory corruption in n/a

> Local attackers can execute arbitrary code via a buffer overflow in luxman when using insecure svgalib libraries.

- **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 needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-693-1, GHSA-823f-9rm4-pfxx

## What is CVE-2005-0385?

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

### Official description

Buffer overflow in luxman before 0.41, if used with certain insecure svgalib libraries, allows local users to execute arbitrary code via a long -f command line argument.

## Which versions are affected by CVE-2005-0385?

It affects 1 product.


Products: Frank Mcingvale Luxman.

## How do I fix CVE-2005-0385?

Upgrade to a fixed version.

## Is CVE-2005-0385 being exploited?

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

Public exploit code:

- Frank McIngvale LuxMan 0.41 - Local Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-1245](https://insights.sbomify.com/CVE-2002-1245/): Path traversal in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0385 and fix it if it is affected.

What it is: CVE-2005-0385 is a high-severity memory corruption vulnerability in n/a, published on 17 Mar 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0385 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-2005-0385/ (Markdown: https://insights.sbomify.com/CVE-2005-0385/index.md)
```

## Sources

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

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