Asr 5000 Series SoftwareApplication · Cisco
CVE-2015-6382
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 devices with software 16.0(900) allow remote attackers to cause a denial of service (telnetd process restart) via a TELNET connection, aka Bug ID CSCuv25815.
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 devices running software version 16.0(900) contain a denial of service vulnerability in the telnetd process. Remote attackers can trigger a process restart by sending specially crafted TELNET connection requests, causing service disruption.
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 Series SoftwareApplication
= 16.0\(900\)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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco ASR 5000 hardwareRun 'show hardware' or check the device model via 'show version' output to confirm the device is an ASR 5000 Series routerAffected if Device is not a Cisco ASR 5000 Series, then not affected by this specific CVE
-
Check exact software versionExecute 'show version' and locate the software version string - this CVE affects only version 16.0(900) exactlyAffected if Version is exactly 16.0(900), proceed to next check; if version differs, not affected by this CVE
-
Verify telnetd process is runningRun 'show process name telnetd' or 'show process cpu' to check if the telnetd process is active on the systemAffected if telnetd process is not running or disabled, the attack surface is reduced but verify telnet access is also disabled
-
Confirm telnet access is enabledCheck telnet server configuration via 'show telnet server' or 'show running-config | include telnet' to see if TELNET is allowed for administrative accessAffected if TELNET is enabled and accessible (even from local console), the vulnerability can be triggered; if only SSH is enabled, the specific attack vector is not accessible
You are affected only if you have a Cisco ASR 5000 running exactly software version 16.0(900) with telnetd enabled and telnet access exposed - all three conditions must be true.
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 software to a version beyond 16.0(900) that addresses Bug ID CSCuv25815, or disable TELNET access and use SSH for administrative access with appropriate firewall/ACL controls.
Fix this in Asr 5000 Series Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6382 — 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-6382 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