CVE-2000-0813
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCheck Point VPN-1/FireWall-1 4.1 and earlier allows remote attackers to redirect FTP connections to other servers ("FTP Bounce") via invalid FTP commands that are processed improperly by FireWall-1, aka "FTP Connection Enforcement Bypass."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCheck Point VPN-1/FireWall-1 4.1 and earlier improperly processes invalid FTP commands in its inspection engine, allowing remote attackers to redirect FTP data connections to arbitrary servers. This enables the classic FTP bounce attack where the firewall can be tricked into establishing connections to third-party targets, bypassing the intended network segmentation controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.0= 4.0= 4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Checkpoint Firewall-1 versionRun 'fwver' on the firewall management console or check the installed package version through the Check Point administration GUI (SmartDashboard) under 'Products' or 'Gateway' propertiesAffected if The installed version is 3.0, 4.0, or 4.1 exactly
-
Confirm FTP inspection is enabledIn the Check Point SmartDashboard, examine the rulebase under 'Service' column for FTP protocol. Check the Inspection column or inspect the 'FTP' service properties in the 'Services' tree to confirm the FTP inspection module is activeAffected if FTP inspection is enabled on the firewall policy and the version is 3.0-4.1
-
Review FTP inspection rules for invalid PORT handlingIn SmartDashboard, open the FTP service properties (Services > FTP) and check the 'Content' or 'Inspection' tab for how PORT commands are handled. Alternatively, examine the rulebase for any rule allowing FTP traffic without strict PORT command validationAffected if The inspection rules do not block or validate invalid PORT commands, or allow arbitrary PORT command destinations
A user is affected if their Checkpoint Firewall-1 version is 3.0, 4.0, or 4.1 AND FTP inspection is active, as this combination allows the FTP bounce attack to succeed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of VPN-1/FireWall-1 beyond 4.1, or implement strict FTP inspection rules that block invalid PORT commands and restrict FTP data channel destinations to prevent connection redirection.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2000-0813 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data