# CVE-2003-1474: Privilege escalation in n/a

> Local users in the games group can modify slashem-tty to execute arbitrary code as other users due to insecure file permissions.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 24 Oct 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-525w-wcmh-7q9w

## What is CVE-2003-1474?

CVE-2003-1474 is a high-severity vulnerability in n/a, published on 24 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

slashem-tty in the FreeBSD Ports Collection is installed with write permissions for the games group, which allows local users with group games privileges to modify slashem-tty and execute arbitrary code as other users, as demonstrated using a separate vulnerability in LTris.

Weakness: CWE-264

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

It affects 1 product.


Products: Freebsd Slashem-Tty.

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

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

## Is CVE-2003-1474 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-1474 is a high-severity vulnerability in n/a, published on 24 Oct 2007. 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-1474 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-1474/ (Markdown: https://insights.sbomify.com/CVE-2003-1474/index.md)
```

## Sources

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

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