# CVE-2004-1295: Missing authorization in n/a

> Local users can disable network interfaces via the uml_net utility due to missing permission checks, causing denial of service.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/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:** No
- **Published:** 22 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xc8g-29h4-jqx5

## What is CVE-2004-1295?

CVE-2004-1295 is a low-severity missing authorization vulnerability in n/a, published on 22 Dec 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The slip_down function in slip.c for the uml_net program in uml-utilities 20030903, when uml_net is installed setuid root, does not verify whether the calling user has sufficient permission to disable an interface, which allows local users to cause a denial of service (network service disabled).

## Which versions are affected by CVE-2004-1295?

It affects 1 product.


Products: Uml-Utilities Uml-Utilities.

## How do I fix CVE-2004-1295?

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

## Is CVE-2004-1295 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1295 and fix it if it is affected.

What it is: CVE-2004-1295 is a low-severity missing authorization vulnerability in n/a, published on 22 Dec 2004. 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-2004-1295 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-2004-1295/ (Markdown: https://insights.sbomify.com/CVE-2004-1295/index.md)
```

## Sources

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

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