# CVE-2003-0188: Path traversal in n/a

> Local attackers can execute arbitrary commands as other users by placing malicious .lv files in directories where the lv viewer reads them.

- **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 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0188, DSA-304, GHSA-mpj5-8r3q-68mq

## What is CVE-2003-0188?

CVE-2003-0188 is a high-severity path traversal vulnerability in Redhat Linux, published on 17 May 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lv reads a .lv file from the current working directory, which allows local users to execute arbitrary commands as other lv users by placing malicious .lv files into other directories.

## Which versions are affected by CVE-2003-0188?

It affects 3 products.


Products: Lv Lv, Redhat Linux, Redhat Lv.

## How do I fix CVE-2003-0188?

Apply the vendor's patch.

## Is CVE-2003-0188 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0188 and fix it if it is affected.

What it is: CVE-2003-0188 is a high-severity path traversal vulnerability in Redhat Linux, published on 17 May 2003. 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-2003-0188 in the wild and no public exploit code.

Affected product: Redhat Linux. 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-2003-0188/ (Markdown: https://insights.sbomify.com/CVE-2003-0188/index.md)
```

## Sources

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

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