dbcve.org
iOSOperating system · Cisco

CVE-2015-0771

MEDIUM · 6.3 CVSS v2.0 Published 2015-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 IKE implementation in the WS-IPSEC-3 service module in Cisco IOS 12.2 on Catalyst 6500 devices allows remote authenticated users to cause a denial of service (device reload) by sending a crafted message during IPsec tunnel setup, aka Bug ID CSCur70505.

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

Denial of service vulnerability in the IKE (Internet Key Exchange) implementation in the WS-IPSEC-3 service module for Cisco IOS 12.2 on Catalyst 6500 switches. An authenticated remote attacker can send a specially crafted message during IPsec tunnel setup that triggers a device reload.

MitigationUpgrade Cisco IOS to a version that addresses CSCur70505, or if the WS-IPSEC-3 module is unused, consider disabling it to reduce attack surface.

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
iOSOperating system
Affected:= 12.2\(33\)sxj8= 12.2sxj

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
M
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/Au:S/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 checks

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

  1. Confirm Catalyst 6500 hardware platform
    Use 'show version' command to verify the device model is Cisco Catalyst 6500 series switch
    Affected if Device is not a Catalyst 6500 series switch - not affected
  2. Verify WS-IPSEC-3 module is installed
    Use 'show module' or 'show hardware' command to check for WS-IPSEC-3 service module in the chassis
    Affected if WS-IPSEC-3 module is not present - not affected
  3. Check Cisco IOS version
    Use 'show version' command and look for IOS version 12.2(33)sxj8 or 12.2sxj specifically
    Affected if IOS version equals 12.2(33)sxj8 or 12.2sxj - potentially affected
  4. Verify IKE/IPsec is configured
    Use 'show crypto isakmp sa' or 'show crypto ipsec sa' commands to check if any IKE/IPsec tunnels are active or configured
    Affected if No IKE/IPsec tunnels are configured and the WS-IPSEC-3 module has no active security associations - lower risk

Device is affected only if it is a Catalyst 6500 with WS-IPSEC-3 module installed, running Cisco IOS 12.2(33)sxj8 or 12.2sxj, and has IKE/IPsec configured or active tunnels.

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

Upgrade Cisco IOS to a version that addresses CSCur70505, or if the WS-IPSEC-3 module is unused, consider disabling it to reduce attack surface.

Fix this in iOS 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-2015-0771 — 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-2015-0771 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