dbcve.org
Cloud Services Platform 2100Application · Cisco

CVE-2017-12251

CRITICAL · 9.9 CVSS v3.0 Published 2017-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
A vulnerability in the web console of the Cisco Cloud Services Platform (CSP) 2100 could allow an authenticated, remote attacker to interact maliciously with the services or virtual machines (VMs) operating remotely on an affected CSP device. The vulnerability is due to weaknesses in the generation of certain authentication mechanisms in the URL of the web console. An attacker could exploit this vulnerability by browsing to one of the hosted VMs' URLs in Cisco CSP and viewing specific patterns that control the web application's mechanisms for authentication control. An exploit could allow the attacker to access a specific VM on the CSP, which causes a complete loss of the system's confidentiality, integrity, and availability. This vulnerability affects Cisco Cloud Services Platform (CSP) 2100 running software release 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, or 2.2.2. Cisco Bug IDs: CSCve64690.

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

A vulnerability in the web console of Cisco Cloud Services Platform (CSP) 2100 allows an authenticated, remote attacker to access hosted VMs by exploiting weaknesses in the URL-based authentication mechanism. The attacker browses to VM URLs and views specific patterns that control the application's authentication controls, achieving complete loss of confidentiality, integrity, and availability on affected VMs.

MitigationUpgrade Cisco CSP 2100 to a fixed software release beyond version 2.2.2. If upgrade is not immediately feasible, restrict web console access to trusted administrators only and monitor for unauthorized VM access attempts.

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
Cloud Services Platform 2100Application
Affected:= 2.1.0= 2.1.1= 2.1.2= 2.2.0= 2.2.1= 2.2.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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 CSP 2100 deployment
    Locate any Cisco Cloud Services Platform 2100 appliances in your inventory or network. Check device hostnames, management interfaces, or documentation for this specific model.
    Affected if Cisco CSP 2100 hardware or virtual appliance is present in the environment
  2. Determine installed software version
    Access the CSP 2100 CLI or web console and run 'show version' or check the system information page to retrieve the exact software version number.
    Affected if Installed version matches 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, or 2.2.2
  3. Verify web console is accessible
    Check if the CSP 2100 web console interface (HTTPS on port 443 or configured port) is reachable from network segments. Use 'show http server' or review firewall policies.
    Affected if Web console is enabled and exposed to network traffic
  4. Review access logs for VM URL patterns
    Examine CSP 2100 web console logs for requests to VM-specific URLs that may indicate unauthorized access attempts. Look for direct VM console or VNC URL patterns.
    Affected if Logs show VM access from unauthenticated or unauthorized user sessions
  5. Check for unauthorized VM sessions
    Use 'show vm sessions' or equivalent command on CSP 2100 to list active or recent VM console sessions and verify they were initiated by legitimate administrators.
    Affected if Active VM sessions exist that were not initiated by known administrators

Your environment is affected if you have a Cisco CSP 2100 running versions 2.1.0 through 2.2.2 with the web console accessible to network users.

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 CSP 2100 to a fixed software release beyond version 2.2.2. If upgrade is not immediately feasible, restrict web console access to trusted administrators only and monitor for unauthorized VM access attempts.

Fix this in Cloud Services Platform 2100 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12251 — 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-2017-12251 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