# CVE-2005-0447: Denial of service in n/a

> Remote attackers can cause a system hang in Solaris by flooding it with specific ARP packets, requiring OS patches.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pr8j-rpfh-vf74

## What is CVE-2005-0447?

CVE-2005-0447 is a medium-severity denial of service vulnerability in Sun Solaris, published on 15 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Solaris 7, 8, and 9 allows remote attackers to cause a denial of service (hang) via a flood of certain ARP packets.

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

It affects 2 products.


Products: Sun Solaris, Sun Sunos.

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

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

## Is CVE-2005-0447 being exploited?

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

What it is: CVE-2005-0447 is a medium-severity denial of service vulnerability in Sun Solaris, published on 15 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0447 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-0447/ (Markdown: https://insights.sbomify.com/CVE-2005-0447/index.md)
```

## Sources

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

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