dbcve.org
Secure Access Control SystemApplication · Cisco

CVE-2017-12354

MEDIUM · 5.3 CVSS v3.0 Published 2017-11-30
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
A vulnerability in the web-based interface of Cisco Secure Access Control System (ACS) could allow an unauthenticated, remote attacker to view sensitive information on an affected system. The vulnerability exists because the affected software does not sufficiently protect system software version information when the software responds to HTTP requests that are sent to the web-based interface of the software. An attacker could exploit this vulnerability by sending crafted HTTP requests to the web-based interface of the affected software. A successful exploit could allow the attacker to view sensitive information about the software, which the attacker could use to conduct additional reconnaissance attacks. Cisco Bug IDs: CSCvf66155.

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

An information disclosure vulnerability in Cisco Secure Access Control System (ACS) web interface allows unauthenticated remote attackers to obtain sensitive software version information through crafted HTTP requests. The vulnerability exists because the affected software does not sufficiently protect system version information when responding to HTTP requests, exposing details that could aid further reconnaissance attacks.

MitigationApply the Cisco patch for CSCvf66155 when available. In the interim, restrict network access to the ACS web-based management interface using firewalls or ACLs, and consider disabling the web interface if not required for operations.

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
Secure Access Control SystemApplication
Affected:= 5.8\(0.32\)

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 ACS web interface is exposed
    Check network listening ports and firewall rules to determine if the ACS web interface (typically ports 80, 443, or 8443) is accessible from untrusted networks. Use 'netstat -an' or firewall inspection to list accessible services.
    Affected if The ACS web interface is accessible from untrusted network segments without authentication barriers.
  2. Determine the installed Cisco ACS version
    Access the ACS administrative interface or check the system using the ACS administration console. The version is typically visible in the web interface login page or in the 'System Administration > Operations' section of the ACS GUI.
    Affected if The installed version is exactly 5.8(0.32).
  3. Test for version information disclosure via HTTP
    Send a crafted HTTP request to the ACS web interface endpoint. For example, use 'curl -v http://<acs-host>/' or similar requests to observe the HTTP response headers and body for version information disclosure.
    Affected if The HTTP response reveals detailed Cisco ACS version information (such as 5.8(0.32)) without requiring authentication.
  4. Verify if web interface requires authentication
    Attempt to access the ACS web interface URL without providing credentials. Observe whether version details or system information is returned before any login prompt appears.
    Affected if Version or system information is displayed to unauthenticated users before any login credential is requested.

If Cisco ACS version 5.8(0.32) is running and its web interface is accessible from an untrusted network, and the HTTP response discloses version information without authentication, the environment is affected by this CVE.

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 the Cisco patch for CSCvf66155 when available. In the interim, restrict network access to the ACS web-based management interface using firewalls or ACLs, and consider disabling the web interface if not required for operations.

Fix this in Secure Access Control System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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