Asr 5000 SoftwareOperating system · Cisco
CVE-2015-6334
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 · uneditedCisco ASR 5000 and 5500 devices with software 18.0.0.57828 and 19.0.M0.61045 allow remote attackers to cause a denial of service (vpnmgr process restart) via a crafted header in a TACACS packet, aka Bug ID CSCuw01984.
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 confidenceCisco ASR 5000 and 5500 devices running software versions 18.0.0.57828 and 19.0.M0.61045 contain a denial of service vulnerability in the vpnmgr process. Attackers can exploit this by sending TACACS packets with a crafted/malformed header, causing the vpnmgr process to restart and disrupting VPN management operations.
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 SoftwareOperating system
= 18.0.0.57828= 19.0.m0.61045CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelRun 'show hardware' or 'show version' command on the Cisco ASR device to confirm the model number is ASR 5000 or ASR 5500Affected if Device is not a Cisco ASR 5000 or 5500, then not affected by this specific CVE
-
Check the installed software versionExecute 'show version' and locate the Software Version field. Compare the exact version number to 18.0.0.57828 and 19.0.M0.61045Affected if Version matches exactly 18.0.0.57828 or 19.0.M0.61045, the device is running a vulnerable version
-
Verify if TACACS is enabledRun 'show tacacs' or check the configuration with 'show running-config | include tacacs' to determine if TACACS authentication is configured on the deviceAffected if TACACS is not enabled, the attack vector is not present though the software version may still be vulnerable
-
Confirm vpnmgr process statusRun 'show process vpnmgr' or 'show session summary' to verify the vpnmgr process is running and handling VPN managementAffected if vpnmgr process is active, the vulnerability can be triggered to cause denial of service
The device is affected if it is a Cisco ASR 5000 or 5500 running exactly version 18.0.0.57828 or 19.0.M0.61045 with TACACS protocol enabled and the vpnmgr process active.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Cisco ASR 5000/5500 software to a patched version beyond 19.0.M0.61045. If immediate patching is not feasible, consider restricting TACACS access through ACLs or network segmentation to limit exposure to untrusted networks.
Fix this in Asr 5000 Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2015-6334 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-6334 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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