dbcve.org
Asr 5000 SoftwareApplication · Cisco

CVE-2015-6340

MEDIUM · 5.0 CVSS v2.0 Published 2015-10-27
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 Proxy Mobile IPv6 (PMIPv6) component in the CDMA implementation on Cisco ASR 5000 devices with software 19.0.M0.60737 allows remote attackers to cause a denial of service (hamgr process restart) via a crafted header in a PMIPv6 packet, aka Bug ID CSCuv63280.

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

The Proxy Mobile IPv6 (PMIPv6) component in the CDMA implementation on Cisco ASR 5000 devices with software 19.0.M0.60737 contains a vulnerability where a remote attacker can send a crafted PMIPv6 packet with a malformed header, causing the hamgr process to restart and resulting in denial of service.

MitigationApply the vendor patch for Bug ID CSCuv63280 or upgrade to a Cisco fixed software version. If patching is not immediately possible, consider network segmentation to limit exposure to untrusted PMIPv6 traffic sources.

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
Asr 5000 SoftwareApplication
Affected:= 19.0.m0.60737

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. Confirm device model is Cisco ASR 5000
    Run 'show hardware' or 'show version' CLI command to verify the device is an ASR 5000 series
    Affected if Device is not a Cisco ASR 5000 - not affected
  2. Check exact software version
    Run 'show version' or 'show software' to display the installed software version number
    Affected if Version is NOT exactly 19.0.M0.60737 - not affected
  3. Verify PMIPv6 feature is enabled
    Run 'show pmipv6 status' or 'show configuration | include pmipv6' to check if Proxy Mobile IPv6 is configured and active
    Affected if PMIPv6 is not configured or enabled - not affected (exploitation requires PMIPv6 to be active)
  4. Confirm CDMA implementation is in use
    Run 'show cdma statistics' or 'show running-config | include cdma' to verify CDMA services are enabled on the system
    Affected if CDMA services are not configured - likely not affected (vulnerability is in the CDMA implementation path)

The system is affected only if it is running exactly version 19.0.M0.60737 AND has PMIPv6 enabled in a CDMA configuration - the crafted packet must target the PMIPv6 component within the CDMA implementation to trigger the hamgr process restart.

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 the vendor patch for Bug ID CSCuv63280 or upgrade to a Cisco fixed software version. If patching is not immediately possible, consider network segmentation to limit exposure to untrusted PMIPv6 traffic sources.

Fix this in Asr 5000 Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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