# CVE-2003-0396: Memory corruption in n/a

> Local attackers can gain privileges via a buffer overflow in setuid ATM utilities on Linux systems.

- **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 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0396, GHSA-8vrg-v3rr-5xmf

## What is CVE-2003-0396?

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

### Official description

Buffer overflow in les for ATM on Linux (linux-atm) before 2.4.1, if used setuid, allows local users to gain privileges via a long -f command line argument.

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

It affects 1 product.


Products: Linux-Atm Linux-Atm.

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

Upgrade to a fixed version.

## Is CVE-2003-0396 being exploited?

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

Public exploit code:

- Linux-ATM LES 2.4 - Command Line Argument Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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