# CVE-2005-3099: Code injection in n/a

> Local attackers can execute arbitrary code via unspecified vulnerabilities in Solaris Xsun and Xprt commands.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/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:** 28 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7f69-xr47-93rv

## What is CVE-2005-3099?

CVE-2005-3099 is a medium-severity code injection vulnerability in Sun Solaris, published on 28 Sep 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in the (1) Xsun and (2) Xprt commands in Solaris 7, 8, 9, and 10 allows local users to execute arbitrary code.

## Which versions are affected by CVE-2005-3099?

It affects 2 products.


Products: Sun Solaris, Sun Sunos.

## How do I fix CVE-2005-3099?

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

## Is CVE-2005-3099 being exploited?

There is no known exploitation of CVE-2005-3099 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-2005-3099 and fix it if it is affected.

What it is: CVE-2005-3099 is a medium-severity code injection vulnerability in Sun Solaris, published on 28 Sep 2005. 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-2005-3099 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-2005-3099/ (Markdown: https://insights.sbomify.com/CVE-2005-3099/index.md)
```

## Sources

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

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