Asr 5000Hardware / appliance · Cisco
CVE-2016-1452
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 18.3 through 20.0.0 allow remote attackers to make configuration changes over SNMP by leveraging knowledge of the read-write community, aka Bug ID CSCuz29526.
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 confidenceThe vulnerability allows remote attackers to make configuration changes on Cisco ASR 5000 devices (software 18.3-20.0.0) via SNMP by obtaining the read-write community string. This grants attackers administrative-level access to modify device configurations remotely.
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 5000Hardware / appliance
all versions
Asr 5000 SoftwareApplication
= 18.3.0= 18.3_base= 19.0.1= 19.0.m0.60737= 19.0.m0.60828= 19.0.m0.61045= 19.1.0= 19.1.0.61559= 19.2.0= 19.3.0= 20.0.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 modelVerify the hardware is a Cisco ASR 5000 series device. Use 'show hardware' or check the device chassis label/model number.Affected if The device is not a Cisco ASR 5000, then it is not affected by this specific CVE.
-
Check the installed software versionExecute 'show version' or 'show software' on the device CLI to retrieve the running software version.Affected if The software version matches any of: 18.3.0, 18.3_base, 19.0.1, 19.0.m0.60737, 19.0.m0.60828, 19.0.m0.61045, 19.1.0, 19.1.0.61559, 19.2.0, 19.3.0, or 20.0.0.
-
Verify SNMP is enabledRun 'show snmp' or 'show snmp community' to check if SNMP is configured and running on the device.Affected if SNMP is disabled or not configured, then the attack vector is not present.
-
Inspect SNMP community string configurationUse 'show snmp community' to view configured SNMP community strings. Check for default or weak read-write community strings such as 'public', 'private', or vendor defaults.Affected if A read-write SNMP community string is configured and is default, weak, or known to an attacker, the device is vulnerable to configuration modification.
The device is affected if it is a Cisco ASR 5000 running software version 18.3.0 through 20.0.0 with SNMP enabled and a default or weak read-write community string configured.
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 dataImmediately change default or weak SNMP read-write community strings to strong, unique values. Implement SNMPv3 with authentication and encryption, and apply access control lists to restrict SNMP management access to authorized IP addresses only.
Fix this in Asr 5000
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1452 — 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-2016-1452 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