dbcve.org
Firewall 1Application · Checkpoint

CVE-1999-0675

MEDIUM · 5.0 CVSS v2.0 Published 1999-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Check Point FireWall-1 can be subjected to a denial of service via UDP packets that are sent through VPN-1 to port 0 of a host.

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 confidence

Check Point FireWall-1 (VPN-1) is vulnerable to a denial of service attack via specially crafted UDP packets sent through the VPN to port 0 of a target host. This causes the firewall or affected host to fail or become unresponsive.

MitigationSince this vulnerability dates from 1999, any affected Check Point installations are extremely outdated and likely end-of-life. Modernize to current Check Point VPN-1/FireWall-1 versions or contemporary firewall solutions; implement network filtering to block malformed UDP traffic to port 0 as an interim measure.

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
Firewall 1Application
Affected:= 3.0= 4.0

CVSS 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
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Check Point Firewall-1 installation
    Run 'fpset' or check /opt/CPfw1-*/ directory for Check Point FireWall-1 installation, or use system package manager to list installed Check Point software
    Affected if Check Point Firewall-1 or VPN-1 is installed on the system
  2. Determine installed version
    Run 'fw ver' command or check version file in /opt/CPfw1-*/ directory
    Affected if Version is 3.0 or 4.0
  3. Verify VPN module is enabled
    Check if VPN-1 module is loaded: run 'fw stat' or check VPN policy configuration via 'cpconfig'
    Affected if VPN-1 functionality is active and configured
  4. Check UDP traffic handling
    Review firewall policy rules to see if UDP traffic is permitted through the VPN tunnel to internal hosts
    Affected if UDP traffic is allowed through the VPN

The system is affected if Check Point Firewall-1 versions 3.0 or 4.0 is installed with VPN-1 enabled and UDP traffic permitted through the VPN

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since this vulnerability dates from 1999, any affected Check Point installations are extremely outdated and likely end-of-life. Modernize to current Check Point VPN-1/FireWall-1 versions or contemporary firewall solutions; implement network filtering to block malformed UDP traffic to port 0 as an interim measure.

Fix this in Firewall 1 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-1999-0675 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-1999-0675 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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