CVE-2005-3673
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 · uneditedThe Internet Key Exchange version 1 (IKEv1) implementation in Check Point products allows remote attackers to cause a denial of service via certain crafted IKE packets, as demonstrated by the PROTOS ISAKMP Test Suite for IKEv1. NOTE: due to the lack of details in the advisory, it is unclear which of CVE-2005-3666, CVE-2005-3667, and/or CVE-2005-3668 this issue applies to.
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 · moderate confidenceA denial of service vulnerability exists in Check Point products' Internet Key Exchange version 1 (IKEv1) implementation. Remote attackers can cause service disruption by sending specially crafted IKE packets, as identified through the PROTOS ISAKMP Test Suite for IKEv1.
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 dataall versions= ci_r57= 3.0= ngx_r60= r54= r55= r55p= r55wCVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 Check Point product installationRun 'cpstat' or check the installed Check Point product package/version using the product's version command (e.g., 'fw ver' for Firewall-1). Inspect system information or Check Point licensing output for the exact product and build number.Affected if The system is running any Check Point product listed in the affected versions (Checkpoint Check Point, Checkpoint Express, Checkpoint Firewall 1, Checkpoint Vpn 1, or Checkpoint Vpn 1 Firewall 1 Next Generation).
-
Verify IKEv1 protocol is enabledCheck the VPN configuration or IKE settings through the Check Point management interface (SmartDashboard/ SmartConsole) or command-line utilities (e.g., 'vpn shell' or 'ikeadmin'). Look for IKE version settings and confirm IKEv1 is actively enabled.Affected if IKEv1 (version 1) protocol is enabled or configured on the VPN gateway. The vulnerability affects only systems using IKEv1; IKEv2-only configurations are not affected.
-
Confirm IKE service is exposed to networkCheck firewall policy rules or network exposure to determine if UDP port 500 (IKE) and UDP port 4500 (NAT-T) are open to external or untrusted networks. Use 'fw stat -l' or review the security policy ruleset.Affected if The IKE service (UDP port 500) is reachable from untrusted external networks. The attack requires sending specially crafted IKE packets to the gateway, so external exposure is required for exploitation.
A system is affected if it runs a Check Point product with IKEv1 enabled and the IKE service is accessible to network attackers who can send malicious IKE packets.
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 dataApply available Check Point vendor patches for this IKEv1 vulnerability. If patches are unavailable, consider blocking or rate-limiting IKE traffic from untrusted external sources at network perimeter, or disable IKEv1 if IKEv2 is supported as an alternative.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3673 — 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-2005-3673 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