dbcve.org
Firewall Services ModuleHardware / appliance · Cisco

CVE-2005-3669

MEDIUM · 5.0 CVSS v2.0 Published 2005-11-18
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
Multiple unspecified vulnerabilities in the Internet Key Exchange version 1 (IKEv1) implementation in multiple Cisco products allow remote attackers to cause a denial of service (device reset) via certain malformed IKE packets, as demonstrated by the PROTOS ISAKMP Test Suite for IKEv1. NOTE: due to the lack of details in the Cisco 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 confidence

Multiple Cisco products contain vulnerabilities in their IKEv1 implementation that allow remote attackers to cause denial of service via malformed IKE packets, resulting in device resets. The vulnerabilities were discovered using the PROTOS ISAKMP Test Suite for IKEv1.

MitigationApply Cisco security patches or software updates for affected products. If patches are unavailable for legacy systems, consider filtering IKE traffic at network boundaries or upgrading to supported versions.

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 Services ModuleHardware / appliance
Affected:all versions= 1.1.2= 1.1.3= 1.1_\(3.005\)= 2.1_\(0.208\)
Vpn 3000 Concentrator Series SoftwareOperating system
Affected:= 2.0= 2.5.2.a= 2.5.2.b= 2.5.2.c= 2.5.2.d= 2.5.2.f= 3.0= 3.0.3.a= 3.0.3.b= 3.0.4= 3.1= 3.1\(rel\)
iOSOperating system
Affected:= 12.2sxd= 12.3t= 12.3tpc= 12.3xd= 12.3xe= 12.3xf= 12.3xg= 12.3xh= 12.3xi= 12.3xj= 12.3xk= 12.3xm
Adaptive Security Appliance SoftwareOperating system
Affected:= 7.0
Pix FirewallApplication
Affected:= 6.2.2_.111= 6.2.3_\(110\)= 6.3.3_\(133\)
Mds 9000Hardware / appliance
Affected:all versions
Mds 9000 San OsOperating system
Affected:= 1.3\(3.33\)= 1.3\(4a\)= 2.0\(0.86\)
Pix Firewall SoftwareOperating system
Affected:= 2.7= 3.0= 3.1= 4.0= 4.1\(6\)= 4.1\(6b\)= 4.2= 4.2\(1\)= 4.2\(2\)= 4.2\(5\)= 4.3= 4.4

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 the Cisco product
    Determine the exact Cisco product model in your environment (FWSM, VPN 3000 Concentrator, iOS, ASA, PIX, or MDS 9000)
    Affected if the product is any of these six product lines mentioned in the affected products list
  2. Check the software version
    Run 'show version' on the device or check the running software version through the management interface
    Affected if the installed version matches any version string listed in the affected products and versions for your product type
  3. Verify IKEv1 is configured
    Check the device configuration for 'isakmp' or 'crypto isakmp' policy definitions, or look for IKE Phase 1 settings in VPN configurations
    Affected if IKEv1 policies or ISAKMP profiles are defined in the running configuration
  4. Confirm IKE is enabled on an interface
    Run 'show crypto isakmp sa' or check interface configurations for 'crypto map' applied to outside/internet-facing interfaces
    Affected if IKE is actively enabled and bound to a functional interface

You are affected if your device runs one of the listed product families AND version combinations AND has IKEv1/ISAKMP configured and enabled on an interface.

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

Apply Cisco security patches or software updates for affected products. If patches are unavailable for legacy systems, consider filtering IKE traffic at network boundaries or upgrading to supported versions.

Fix this in Firewall Services Module Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-3669 — 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-2005-3669 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