Prime Network RegistrarApplication · Cisco
CVE-2016-1427
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 · uneditedThe System Configuration Protocol (SCP) core messaging interface in Cisco Prime Network Registrar 8.2 before 8.2.3.1 and 8.3 before 8.3.2 allows remote attackers to obtain sensitive information via crafted SCP messages, aka Bug ID CSCuv35694.
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 System Configuration Protocol (SCP) core messaging interface in Cisco Prime Network Registrar versions 8.2 before 8.2.3.1 and 8.3 before 8.3.2 contains a vulnerability that allows remote attackers to obtain sensitive information by sending crafted SCP messages to the affected system.
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
Prime Network RegistrarApplication
= 8.2.0= 8.2.0.1= 8.2.0.2= 8.2.1= 8.2.1.1= 8.2.2= 8.2.2.1= 8.2.3= 8.3.0= 8.3.1CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed Cisco Prime Network Registrar versionRun the command 'show version' or check the product GUI for the exact version number. On the CLI, log in and execute 'show system' or look at the startup banner.Affected if The installed version matches 8.2.0 through 8.2.3 (any 8.2.x before 8.2.3.1) or 8.3.0 through 8.3.1 (any 8.3.x before 8.3.2)
-
Verify the SCP service is running and accessibleCheck if the System Configuration Protocol (SCP) service is active. Look for listening ports associated with SCP (typically port 3215 or as configured). Use 'netstat -an | grep <scp-port>' or check the service status via the administrative interface.Affected if The SCP service is enabled and exposed on a network interface accessible to attackers
-
Determine SCP interface exposureReview firewall rules and network ACLs to determine if the SCP port is reachable from untrusted networks. Check the Cisco Prime Network Registrar management interface for allowed hosts or access lists.Affected if The SCP interface is reachable from external or untrusted network segments without proper filtering
You are affected if Cisco Prime Network Registrar version is 8.2.x before 8.2.3.1 or 8.3.x before 8.3.2 AND the SCP interface is enabled and accessible to potential attackers.
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 dataApply the vendor-supplied patches: upgrade to Cisco Prime Network Registrar 8.2.3.1 or 8.3.2 or later. No workarounds are mentioned in the available description.
Fix this in Prime Network Registrar
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1427 — 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-1427 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