dbcve.org
Asa 5500Hardware / appliance · Cisco

CVE-2010-4354

MEDIUM · 5.0 CVSS v2.0 Published 2010-11-30
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
The remote-access IPSec VPN implementation on Cisco Adaptive Security Appliances (ASA) 5500 series devices, PIX Security Appliances 500 series devices, and VPN Concentrators 3000 series devices responds to an Aggressive Mode IKE Phase I message only when the group name is configured on the device, which allows remote attackers to enumerate valid group names via a series of IKE negotiation attempts, aka Bug ID CSCtj96108, a different vulnerability than CVE-2005-2025.

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

Cisco ASA 5500, PIX 500, and VPN Concentrator 3000 series devices have an information disclosure vulnerability in their IPSec VPN implementation. When receiving Aggressive Mode IKE Phase 1 messages, the device only responds when a valid group name is configured, allowing remote attackers to enumerate valid group names through repeated IKE negotiation attempts.

MitigationDisable IKE Aggressive Mode on affected VPN devices and enforce Main Mode for IKE Phase 1 negotiations, or implement rate limiting on IKE negotiation attempts to prevent enumeration.

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
Asa 5500Hardware / appliance
Affected:all versions
Pix 500Hardware / appliance
Affected:all versions
Vpn 3000 ConcentratorHardware / appliance
Affected:all versions
Vpn 3005 ConcentratorHardware / appliance
Affected:all versions
Vpn 3015 ConcentratorHardware / appliance
Affected:all versions
Vpn 3020 ConcentratorHardware / appliance
Affected:all versions
Vpn 3030 ConcentatorHardware / appliance
Affected:all versions
Vpn 3060 ConcentratorHardware / appliance
Affected:all versions

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
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 checks

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

  1. Identify device model
    Run 'show version' or check device inventory to confirm the hardware model (ASA 5500, PIX 500, or VPN 3000 series Concentrator)
    Affected if Device is a Cisco ASA 5500, PIX 500, or any VPN 3000 Concentrator model (3005, 3015, 3020, 3030, 3060)
  2. Verify IPSec VPN is configured
    Run 'show crypto isakmp sa' or 'show vpn-sessiondb' to check for active or configured IPSec VPN tunnels
    Affected if IPSec VPN tunnels or IKE Security Associations exist on the device
  3. Check for IKE Aggressive Mode policies
    Run 'show crypto isakmp policy' or 'show run crypto isakmp' to list IKE Phase 1 policies and identify any using aggresive-mode
    Affected if Any IKE policy explicitly sets 'mode aggressive' or uses Aggressive Mode for VPN group authentication
  4. Inspect VPN group configuration
    Run 'show run crypto isakmp' and look for group configuration under 'crypto isakmp client configuration group' or tunnel-group settings
    Affected if Any group names are configured for IPSec VPN client or LAN-to-LAN connections that use IKE authentication
  5. Confirm group enumeration exposure
    Review logs or perform a test IKE negotiation attempt with an invalid group name and observe if the device sends a response
    Affected if Device responds to IKE Aggressive Mode packets with group-specific errors (valid group produces different response than invalid group)

The environment is affected if the device is a Cisco ASA 5500, PIX 500, or VPN 3000 series Concentrator with IPSec VPN configured and IKE Aggressive Mode enabled for any group-based VPN configuration.

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

Disable IKE Aggressive Mode on affected VPN devices and enforce Main Mode for IKE Phase 1 negotiations, or implement rate limiting on IKE negotiation attempts to prevent enumeration.

Fix this in Asa 5500 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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