Secure Access Control ServerApplication · Cisco
CVE-2015-6345
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 · uneditedSQL injection vulnerability in the Solution Engine in Cisco Secure Access Control Server (ACS) 5.7(0.15) allows remote authenticated users to execute arbitrary SQL commands via a crafted URL, aka Bug ID CSCuw24700.
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 vulnerability in Cisco Secure Access Control Server (ACS) Solution Engine version 5.7(0.15) allows remote authenticated users to execute arbitrary SQL commands via a crafted URL parameter.
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 ServerApplication
= 5.7.0.15CVSS 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 Cisco ACS installationLocate the Cisco Secure Access Control Server installation. On the ACS server, check the version via the web interface (login and view About page) or via CLI: 'show version' or 'acs show version'Affected if The product is Cisco Secure Access Control Server (ACS) Solution Engine
-
Verify exact version numberConfirm the installed version is 5.7(0.15). Check the web interface: log in and navigate to System Administration > Operations > About Cisco Secure ACS, or use CLI command 'acs show version'Affected if Version is exactly 5.7.0.15 (5.7(0.15))
-
Confirm web interface is exposedCheck if the Cisco ACS web interface (default ports 443 or 8443) is accessible from network locations where untrusted users could send requests. Review firewall rules or ACLs controlling access to the ACS management web ports.Affected if The ACS web interface is accessible to remote network users beyond trusted administrators
-
Check remote authentication configurationReview ACS configuration to determine if remote authentication (RADIUS, TACACS+, or LDAP) is enabled, allowing non-console users to authenticate. Check under Access Policies > Device Administration > Identity or similar identity stores configuration.Affected if Remote authentication is enabled, permitting authenticated users access to the web interface
You are affected if Cisco ACS Solution Engine version 5.7.0.15 is running with its web interface accessible to remote authenticated users.
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 dataApply the vendor patch for Cisco ACS 5.7(0.15) or upgrade to a patched version. Until patched, limit and monitor authenticated user access strictly.
Fix this in Secure Access Control Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6345 — 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-6345 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