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

> Local attackers can gain root privileges by exploiting hard link creation and file deletion flaws in the cci_dir function.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 Jul 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jx8m-xm6x-225q

## What is CVE-2003-0578?

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

### Official description

cci_dir in IBM U2 UniVerse 10.0.0.9 and earlier creates hard links and unlinks files as root, which allows local users to gain privileges by deleting and overwriting arbitrary files.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Ibm U2 Universe.

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

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

## Is CVE-2003-0578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0580](https://insights.sbomify.com/CVE-2003-0580/): Memory corruption in n/a (high 7.2)
- [CVE-2002-1450](https://insights.sbomify.com/CVE-2002-1450/): Denial of service in n/a (medium 5.0)
- [CVE-2003-0579](https://insights.sbomify.com/CVE-2003-0579/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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