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

> Remote attackers can crash Juniper NetScreen-Security Manager server components by sending long crafted strings to specific ports.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3x85-87vg-8622

## What is CVE-2005-4587?

CVE-2005-4587 is a high-severity denial of service vulnerability in n/a, published on 30 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Juniper NetScreen-Security Manager (NSM) 2004 FP2 and FP3 allow remote attackers to cause a denial of service (crash or hang of server components that are automatically restarted) via a long crafted string on (1) port 7800 (the GUI Server port) or (2) port 7801 (the Device Server port).

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

It affects 1 product.


Products: Juniper Netscreen-Security Manager 2004.

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

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

## Is CVE-2005-4587 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4587 and fix it if it is affected.

What it is: CVE-2005-4587 is a high-severity denial of service vulnerability in n/a, published on 30 Dec 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-4587 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-2005-4587/ (Markdown: https://insights.sbomify.com/CVE-2005-4587/index.md)
```

## Sources

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

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