Cisco Policy SuiteApplication · Cisco

CVE-2016-1357

MEDIUM · 5.3 CVSS v3.0 Published 2016-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 password-management administration component in Cisco Policy Suite (CPS) 7.0.1.3, 7.0.2, 7.0.2-att, 7.0.3-att, 7.0.4-att, and 7.5.0 allows remote attackers to bypass intended RBAC restrictions and read unspecified data via unknown vectors, aka Bug ID CSCut85211.

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 · moderate confidence

RBAC bypass vulnerability in Cisco Policy Suite's password-management administration component allows remote unauthenticated attackers to bypass role-based access controls and read unspecified sensitive data. The vulnerability affects versions 7.0.1.3 through 7.5.0.

MitigationApply Cisco-supplied patches for CPS versions 7.0.x and 7.5.0; if patches unavailable, implement network segmentation to restrict access to the admin interface to trusted management networks only.

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
Cisco Policy SuiteApplication
Affected:= 7.0.1.3= 7.0.2= 7.0.2-att= 7.0.3-att= 7.0.4-att= 7.0.5

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

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

  1. Identify if Cisco Policy Suite is deployed
    Inventory your systems for Cisco Policy Suite installations. Check for processes named 'cps' or services related to Cisco Policy Suite running on the system.
    Affected if CPS is installed and running in the environment
  2. Determine installed CPS version
    Use the appropriate command or configuration file to retrieve the CPS version (e.g., via CLI 'show version' if accessible, or check version files in the CPS installation directory). Compare the version number to the affected range 7.0.1.3 through 7.5.0.
    Affected if Installed version falls within 7.0.1.3 to 7.5.0 inclusive
  3. Verify password-management admin component accessibility
    Check if the password-management administration interface is exposed and accessible. This typically involves checking the web interface or API endpoints related to password management under the admin functions.
    Affected if The password-management admin component is accessible via network
  4. Confirm admin interface is reachable without authentication
    Attempt to access the admin interface or password-management endpoints without providing credentials. Check if the RBAC enforcement is present or if unauthenticated requests are accepted.
    Affected if The admin interface can be reached and certain sensitive data is accessible without authentication

A user is affected if Cisco Policy Suite version 7.0.1.3 through 7.5.0 is installed AND the password-management admin component is network-accessible, allowing unauthenticated users to bypass RBAC and read sensitive data.

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

Apply Cisco-supplied patches for CPS versions 7.0.x and 7.5.0; if patches unavailable, implement network segmentation to restrict access to the admin interface to trusted management networks only.

Fix this in Cisco Policy Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1357 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1357 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