Prime Network Control SystemApplication · Cisco
CVE-2015-0768
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 Device Work Center (DWC) component in Cisco Prime Network Control System (NCS) 2.1(0.0.85), 2.2(0.0.58), and 2.2(0.0.69) does not properly implement AAA roles, which allows remote authenticated users to bypass intended access restrictions and execute commands via a login session, aka Bug ID CSCur27371.
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 Device Work Center (DWC) component in Cisco Prime Network Control System versions 2.1(0.0.85), 2.2(0.0.58), and 2.2(0.0.69) contains a role-based access control (RBAC) bypass vulnerability where AAA role enforcement is not properly implemented. Authenticated users can bypass intended access restrictions and execute privileged commands through the DWC component by manipulating their login session, despite being assigned to roles that should not permit such access.
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 Control SystemApplication
= 2.1\(0.0.85\)= 2.2\(0.0.58\)= 2.2\(0.0.69\)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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/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 installed Cisco Prime NCS versionLog into the NCS admin interface and navigate to the About or System Information page, or run 'show version' command via CLI if accessibleAffected if The installed version matches exactly 2.1(0.0.85), 2.2(0.0.58), or 2.2(0.0.69)
-
Verify Device Work Center component accessibilityAttempt to access the DWC component interface via the NCS web UI, typically found under the Device Work Center menu or equivalent administrative sectionAffected if DWC component is accessible and functional in the environment
-
Review AAA role assignments for usersUse the NCS administrative interface to list all users and their assigned AAA roles. Check for users assigned to roles that should have restricted command execution permissionsAffected if Users with limited roles have access to privileged commands they should not possess, indicating the RBAC bypass is present
-
Inspect user session tokens and role enforcementExamine the session management logs or use browser developer tools to inspect session cookies/tokens when accessing DWC. Compare actual permissions granted versus what the assigned role should permitAffected if Session role claims do not match the user's assigned AAA role, or privileged commands execute despite restricted role assignment
Your environment is affected if you are running exactly version 2.1(0.0.85), 2.2(0.0.58), or 2.2(0.0.69) of Cisco Prime Network Control System and users can execute privileged commands through the Device Work Center that their assigned AAA roles should not permit.
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 relevant Cisco patch for this vulnerability (refer to Cisco bug ID CSCur27371). If no patch is available, verify and restrict AAA role assignments to ensure users only have permissions appropriate to their job function, and consider network segmentation to limit exposure of the NCS management interface.
Fix this in Prime Network Control System
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-2015-0768 — 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-0768 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