# CVE-2000-0805: Other in n/a

> Attackers can trigger improper retransmission of encapsulated packets, potentially causing denial of service or resource exhaustion on Check Point VPN-1/FireWall-1 devices.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 22 Jan 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6f6v-7779-324h

## What is CVE-2000-0805?

CVE-2000-0805 is a high-severity vulnerability in n/a, published on 22 Jan 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Check Point VPN-1/FireWall-1 4.1 and earlier improperly retransmits encapsulated FWS packets, even if they do not come from a valid FWZ client, aka "Retransmission of Encapsulated Packets."

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

It affects 1 product.


Products: Checkpoint Firewall-1.

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

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

## Is CVE-2000-0805 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0040](https://insights.sbomify.com/CVE-2004-0040/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0469](https://insights.sbomify.com/CVE-2004-0469/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0039](https://insights.sbomify.com/CVE-2004-0039/): Code injection in n/a (critical 10.0)
- [CVE-2004-2679](https://insights.sbomify.com/CVE-2004-2679/): Information disclosure in n/a (high 7.8)
- [CVE-2004-0699](https://insights.sbomify.com/CVE-2004-0699/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0805 is a high-severity vulnerability in n/a, published on 22 Jan 2001. 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-2000-0805 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-2000-0805/ (Markdown: https://insights.sbomify.com/CVE-2000-0805/index.md)
```

## Sources

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

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