CVE-2004-2679
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 Firewall-1 4.1 up to NG AI R55 allows remote attackers to obtain potentially sensitive information by sending an Internet Key Exchange (IKE) with a certain Vendor ID payload that causes Firewall-1 to return a response containing version and other information.
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 Firewall-1 versions 4.1 through NG AI R55 contains an information disclosure vulnerability in its IKE (Internet Key Exchange) implementation. Attackers can send a specially crafted IKE packet containing a particular Vendor ID payload, causing the firewall to respond with version information and potentially other sensitive system details.
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= 4.0= 4.1= r55CVSS 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
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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.
-
Confirm Check Point Firewall-1 installationCheck for the presence of Check Point Firewall-1 software on the system. On the management console, run 'cpstat -h' or check the installed packages using the Check Point product catalog command if available.Affected if Check Point Firewall-1 is not installed on the system.
-
Identify installed Firewall-1 versionRetrieve the exact version of Check Point Firewall-1 installed. This can typically be done via the Check Point SmartDashboard under 'Gateway Properties', or by running 'cpinfo -y all' on the gateway, or checking the installation history.Affected if The installed version is 4.0, 4.1, or R55 (NG AI R55).
-
Verify IKE service statusDetermine whether IKE (Internet Key Exchange) is enabled on the Firewall-1 gateway. This can be checked through SmartDashboard under VPN > IKE, or via 'vpn ver' command output, or by reviewing the gateway's IPSec/IKE configuration settings.Affected if IKE service is actively enabled and configured on the firewall.
-
Assess network exposure of IKE serviceReview firewall rulebase and network accessibility to determine if IKE traffic (UDP port 500) can reach the Firewall-1 gateway from untrusted networks. Check perimeter ACLs or external interface rules.Affected if IKE traffic from external or untrusted networks can reach the firewall's external interface.
A system is affected if it runs Check Point Firewall-1 version 4.0, 4.1, or R55 with IKE enabled and accessible from networks where attackers could send the specially crafted IKE Vendor ID payload.
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 current supported version of Check Point Firewall-1/Quantum. If immediate upgrade is not feasible, consider restricting IKE traffic at network perimeter devices to limit external attackers' ability to probe for this information.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2679 — 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-2004-2679 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