# CVE-2001-0589: Security feature bypass in n/a

> A local attacker can bypass DMZ denial policies on NetScreen devices using specific traffic patterns, compromising network segmentation.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/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:** 9 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-f8gc-rwq9-w3v6

## What is CVE-2001-0589?

CVE-2001-0589 is a low-severity vulnerability in n/a, published on 9 Mar 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NetScreen ScreenOS prior to 2.5r6 on the NetScreen-10 and Netscreen-100 can allow a local attacker to bypass the DMZ 'denial' policy via specific traffic patterns.

## Which versions are affected by CVE-2001-0589?

It affects 1 product.


Products: Juniper Netscreen Screenos.

## How do I fix CVE-2001-0589?

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

## Is CVE-2001-0589 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-0059](https://insights.sbomify.com/CVE-2018-0059/): ScreenOS: Stored Cross-Site Scripting (XSS) vulnerability (medium 5.4)
- [CVE-2002-2150](https://insights.sbomify.com/CVE-2002-2150/): Denial of service in n/a (medium 5.0)
- [CVE-2004-1446](https://insights.sbomify.com/CVE-2004-1446/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1547](https://insights.sbomify.com/CVE-2002-1547/): Denial of service in n/a (medium 5.0)
- [CVE-2002-0891](https://insights.sbomify.com/CVE-2002-0891/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0589 and fix it if it is affected.

What it is: CVE-2001-0589 is a low-severity vulnerability in n/a, published on 9 Mar 2002. 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-2001-0589 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-2001-0589/ (Markdown: https://insights.sbomify.com/CVE-2001-0589/index.md)
```

## Sources

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

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