Secure Access Control SystemApplication · Cisco
CVE-2015-0580
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 · uneditedMultiple SQL injection vulnerabilities in the ACS View reporting interface pages in Cisco Secure Access Control System (ACS) before 5.5 patch 7 allow remote authenticated administrators to execute arbitrary SQL commands via crafted HTTPS requests, aka Bug ID CSCuq79027.
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 confidenceSQL injection vulnerabilities exist in the ACS View reporting interface of Cisco Secure Access Control System (ACS) before version 5.5 patch 7. Authenticated remote administrators can execute arbitrary SQL commands via crafted HTTPS requests to the reporting pages.
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
<= 5.5.0.46CVSS 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 ACS versionLog into the ACS admin console and navigate to System Administration > System Configuration > Logging Deployment, or check the ACS version via the CLI command 'show version' or 'acs info'Affected if The installed version is 5.5.0.46 or earlier (any version up to and including 5.5.0.46)
-
Confirm ACS View reporting interface is enabledCheck if the ACS View component is installed and enabled on the ACS server. This is typically accessible via the ACS admin web interface under the reporting or monitoring sectionsAffected if ACS View reporting interface is present and accessible via HTTPS on the reporting pages
-
Verify administrative access exposureDetermine if the ACS administrative web interface (HTTPS) is reachable from network segments beyond trusted administration networks. Check firewall rules or ACLs controlling access to TCP port 443 or 8443 on the ACS serverAffected if The ACS admin/reporting interface is exposed to untrusted or external network segments
-
Review ACS user accounts with administrative privilegesExamine the ACS internal user database or external identity sources (LDAP/AD) to identify accounts granted administrative or reporting privileges. Use the ACS admin console to list accounts with reporting accessAffected if There are administrative or reporting user accounts that could be compromised to exploit the SQL injection
You are affected if Cisco ACS version is 5.5.0.46 or earlier AND the ACS View reporting interface is accessible to authenticated administrators, particularly if exposed beyond trusted networks.
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 dataUpgrade Cisco ACS to version 5.5 patch 7 or later to remediate the SQL injection vulnerability. Alternatively, restrict administrative access to trusted personnel and implement network segmentation to limit exposure.
Fix this in Secure Access Control System
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0580 — 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-0580 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