dbcve.org
Prime Security ManagerApplication · Cisco

CVE-2016-1301

HIGH · 8.8 CVSS v3.0 Published 2016-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The RBAC implementation in Cisco ASA-CX Content-Aware Security software before 9.3.1.1(112) and Cisco Prime Security Manager (PRSM) software before 9.3.1.1(112) allows remote authenticated users to change arbitrary passwords via a crafted HTTP request, aka Bug ID CSCuo94842.

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 confidence

The RBAC (Role-Based Access Control) implementation in Cisco ASA-CX Content-Aware Security software and Cisco Prime Security Manager (PRSM) software contains a broken authentication vulnerability. A remote authenticated user can change arbitrary user passwords by sending a crafted HTTP request, effectively allowing privilege escalation and account takeover of any user account.

MitigationUpgrade Cisco ASA-CX and PRSM software to version 9.3.1.1(112) or later to patch the RBAC bypass vulnerability. Review user accounts for unauthorized changes after applying the update.

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 Security ManagerApplication
Affected:= 9.0.0= 9.0.1-40= 9.0.2-68= 9.1.0= 9.1.2-29= 9.1.2-42= 9.1.3-8= 9.1.3-10= 9.1.3-13= 9.2.0= 9.2.1-1= 9.2.1-2
Asa Cx Context Aware Security SoftwareOperating system
Affected:= 9.0.1= 9.0.1-40= 9.0.2= 9.0.2-68= 9.0_base= 9.1.2-29= 9.1.2-42= 9.1.3-8= 9.1.3-10= 9.1.3-13= 9.2.1-1= 9.2.1-2

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco PRSM version
    Access the PRSM administrative interface or check the version via CLI using 'show version' or inspect the software release notes. Compare the installed version number against the listed affected versions (9.0.0 through 9.2.1-2).
    Affected if The installed PRSM version matches any of the following ranges: 9.0.0, 9.0.1-40, 9.0.2-68, 9.1.0, 9.1.2-29, 9.1.2-42, 9.1.3-8, 9.1.3-10, 9.1.3-13, 9.2.0, 9.2.1-1, or 9.2.1-2.
  2. Identify Cisco ASA-CX version
    Access the ASA-CX management console or check the version via CLI using 'show version'. Compare against the listed affected versions.
    Affected if The installed ASA-CX version matches any of the following: 9.0.1, 9.0.1-40, 9.0.2, 9.0.2-68, 9.0_base, 9.1.2-29, 9.1.2-42, 9.1.3-8, 9.1.3-10, 9.1.3-13, 9.2.1-1, or 9.2.1-2.
  3. Verify HTTP management interface is accessible
    Confirm that the web-based management interface for PRSM or ASA-CX is exposed and accessible on the network. This is the attack vector for the crafted HTTP request.
    Affected if The HTTP management interface is exposed and allows authenticated access to users.
  4. Review user account modifications
    Examine PRSM or ASA-CX audit logs, user account records, or authentication logs for any unexpected password changes, privilege escalations, or account modifications that were not performed by an authorized administrator.
    Affected if There are user password changes or account modifications that were not initiated by the legitimate administrator.

You are affected if either PRSM or ASA-CX is running a version within the listed ranges and the HTTP management interface is accessible, or if unauthorized user account changes are found in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco ASA-CX and PRSM software to version 9.3.1.1(112) or later to patch the RBAC bypass vulnerability. Review user accounts for unauthorized changes after applying the update.

Fix this in Prime Security Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1301 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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