# CVE-2000-0613: Denial of service in n/a

> Remote attackers can force the Cisco Secure PIX Firewall to close legitimate connections by sending forged TCP Reset packets.

- **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:** 13 Oct 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-pxcf-v9c2-vw3r

## What is CVE-2000-0613?

CVE-2000-0613 is a medium-severity denial of service vulnerability in n/a, published on 13 Oct 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Secure PIX Firewall does not properly identify forged TCP Reset (RST) packets, which allows remote attackers to force the firewall to close legitimate connections.

## Which versions are affected by CVE-2000-0613?

It affects 1 product.


Products: Cisco Pix Firewall.

## How do I fix CVE-2000-0613?

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

## Is CVE-2000-0613 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0613 exists.

Public exploit code:

- PIX Firewall 2.7/3.x/4.x/5 - Forged TCP RST (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-1003](https://insights.sbomify.com/CVE-2003-1003/): Denial of service in n/a (high 7.8)
- [CVE-1999-1582](https://insights.sbomify.com/CVE-1999-1582/): Misconfiguration in n/a (high 7.5)
- [CVE-2002-0954](https://insights.sbomify.com/CVE-2002-0954/): Weak cryptography in n/a (high 7.5)
- [CVE-2003-1004](https://insights.sbomify.com/CVE-2003-1004/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0613 and fix it if it is affected.

What it is: CVE-2000-0613 is a medium-severity denial of service vulnerability in n/a, published on 13 Oct 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0613 exists.

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-2000-0613/ (Markdown: https://insights.sbomify.com/CVE-2000-0613/index.md)
```

## Sources

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

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