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

> Local attackers can overwrite arbitrary files via insecure temporary file creation in the liece Emacs IRC client, potentially escalating privileges.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 10 Jul 2003
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2003-0537, DSA-341, GHSA-m84h-56qv-2fh5

## What is CVE-2003-0537?

CVE-2003-0537 is a medium-severity path traversal vulnerability in n/a, published on 10 Jul 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The liece Emacs IRC client 2.0+0.20030527 and earlier creates temporary files insecurely, which could allow local users to overwrite arbitrary files as other users.

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

It affects 1 product.


Products: Daiki Ueno Liece Emacs Irc Client.

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

Apply the vendor's patch.

## Is CVE-2003-0537 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0537 is a medium-severity path traversal vulnerability in n/a, published on 10 Jul 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-0537 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-2003-0537/ (Markdown: https://insights.sbomify.com/CVE-2003-0537/index.md)
```

## Sources

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

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