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

> Local and remote attackers can gain privileges on HP Tru64 UNIX due to improper RSA signature handling when digital certificates are used.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2003
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x74c-xcwx-4h73

## What is CVE-2003-0724?

CVE-2003-0724 is a high-severity vulnerability in n/a, published on 3 Sep 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ssh on HP Tru64 UNIX 5.1B and 5.1A does not properly handle RSA signatures when digital certificates and RSA keys are used, which could allow local and remote attackers to gain privileges.

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

It affects 1 product.


Products: Compaq Tru64.

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

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

## Is CVE-2003-0724 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0196](https://insights.sbomify.com/CVE-2003-0196/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0161](https://insights.sbomify.com/CVE-2003-0161/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-2002](https://insights.sbomify.com/CVE-2002-2002/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1202](https://insights.sbomify.com/CVE-2002-1202/): Information disclosure in n/a (high 7.5)
- [CVE-2002-0816](https://insights.sbomify.com/CVE-2002-0816/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0724 is a high-severity vulnerability in n/a, published on 3 Sep 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0724 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-0724/ (Markdown: https://insights.sbomify.com/CVE-2003-0724/index.md)
```

## Sources

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

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