Ios XeOperating system · Cisco

CVE-2015-0650

HIGH · 7.8 CVSS v2.0 Published 2015-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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 Service Discovery Gateway (aka mDNS Gateway) in Cisco IOS 12.2, 12.4, 15.0, 15.1, 15.2, 15.3, and 15.4 and IOS XE 3.9.xS and 3.10.xS before 3.10.4S, 3.11.xS before 3.11.3S, 3.12.xS before 3.12.2S, and 3.13.xS before 3.13.1S allows remote attackers to cause a denial of service (device reload) by sending malformed mDNS UDP packets over (1) IPv4 or (2) IPv6, aka Bug ID CSCup70579.

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

A denial of service vulnerability exists in Cisco's Service Discovery Gateway (mDNS Gateway) feature across multiple IOS and IOS XE versions. Remote attackers can send malformed mDNS UDP packets over IPv4 or IPv6, causing the affected device to reload. The vulnerability requires no authentication and can be exploited remotely.

MitigationUpgrade Cisco IOS/IOS XE to the patched versions (IOS XE 3.10.4S, 3.11.3S, 3.12.2S, 3.13.1S or later). If upgrading is not immediately feasible, disable the mDNS Gateway feature if not required.

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
Ios XeOperating system
Affected:= 3.9s.0= 3.9s.1= 3.9s.2= 3.10s.0= 3.10s.0a= 3.10s.1= 3.10s.2= 3.10s.3= 3.11s.0= 3.11s.1= 3.11s.2= 3.12s.0
iOSOperating system
Affected:= 12.2= 12.4= 15.0= 15.1= 15.2= 15.3= 15.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
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 checks

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

  1. Identify the IOS or IOS XE version
    Use the command 'show version' on the device console or via SSH to retrieve the running IOS/IOS XE version string.
    Affected if The version falls within the affected ranges: IOS XE 3.9S.x through 3.12S.0, or iOS versions 12.2, 12.4, 15.0, 15.1, 15.2, 15.3, or 15.4 (any subversion within these trains).
  2. Confirm mDNS Gateway feature is enabled
    Execute 'show mdns gateway' or 'show running-config | include mdns' to check if the Service Discovery Gateway (mDNS) feature is configured on the device.
    Affected if The mDNS Gateway feature is actively enabled or configured on the device.
  3. Verify mDNS service is listening
    Run 'show mdns service statistics' or check if UDP port 5353 (mDNS) is bound to any interface via 'show ip interface' and confirm mDNS service is operational.
    Affected if The device is actively processing mDNS multicast traffic on any interface.

You are affected if your device runs an affected iOS or IOS XE version listed in the CVE and has the mDNS Gateway feature enabled and operational.

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/IOS XE to the patched versions (IOS XE 3.10.4S, 3.11.3S, 3.12.2S, 3.13.1S or later). If upgrading is not immediately feasible, disable the mDNS Gateway feature if not required.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0650 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0650 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