# CVE-2003-0999: Other in n/a

> Multiple vulnerabilities in Solaris lpstat and libprint allow attackers to execute arbitrary code or read and write arbitrary files.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 17 Dec 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v5fj-rmh3-3rm5

## What is CVE-2003-0999?

CVE-2003-0999 is a high-severity vulnerability in Sun Solaris, published on 17 Dec 2003. 

### Official description

Unknown multiple vulnerabilities in (1) lpstat and (2) the libprint library in Solaris 2.6 through 9 may allow attackers to execute arbitrary code or read or write arbitrary files.

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

It affects 2 products.


Products: Sun Solaris, Sun Sunos.

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

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

## Is CVE-2003-0999 being exploited?

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

## Other vulnerabilities in Sun Solaris

- [CVE-2008-3869](https://insights.sbomify.com/CVE-2008-3869/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-3870](https://insights.sbomify.com/CVE-2008-3870/): Integer overflow in n/a (critical 10.0)
- [CVE-2008-4556](https://insights.sbomify.com/CVE-2008-4556/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-3093](https://insights.sbomify.com/CVE-2007-3093/): Code injection in n/a (critical 10.0)
- [CVE-2003-1081](https://insights.sbomify.com/CVE-2003-1081/): Path traversal in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0999 is a high-severity vulnerability in Sun Solaris, published on 17 Dec 2003. 
Exploitation: There is no known exploitation of CVE-2003-0999 in the wild and no public exploit code.

Affected product: Sun Solaris. 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-0999/ (Markdown: https://insights.sbomify.com/CVE-2003-0999/index.md)
```

## Sources

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

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