Secure Access Control Server Solution EngineApplication · Cisco
CVE-2015-0700
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 · uneditedCross-site request forgery (CSRF) vulnerability in the Dashboard page in the monitoring-and-report section in Cisco Secure Access Control Server Solution Engine before 5.5(0.46.5) allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCuj62924.
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 confidenceCross-site request forgery (CSRF) vulnerability in the Dashboard page of the monitoring-and-reporting section in Cisco Secure Access Control Server Solution Engine allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into executing malicious requests.
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 Server Solution EngineApplication
= 5.4.0.46.6= 5.5.0.36= 5.5.0.46.4CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/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 the installed ACS versionLog into the Cisco ACS administrative interface and navigate to System Administration > System Configuration > Logging Deployment, or check the version displayed on the login page and in the About section. Alternatively, use the command line: show version or acs/show version from the ACS console.Affected if The displayed version matches 5.4.0.46.6, 5.5.0.36, or 5.5.0.46.4 exactly.
-
Verify ACS web interface is accessibleAttempt to reach the ACS web administration interface over HTTPS/HTTP from a browser or using curl/wget to confirm the service is running and responding.Affected if The ACS web interface is reachable and responds with the Cisco Secure ACS login page.
-
Confirm Dashboard monitoring-and-reporting accessAfter authenticating, navigate to the Dashboard section under the monitoring-and-reporting area. Check if the page loads successfully.Affected if The Dashboard monitoring-and-reporting page is accessible to authenticated users.
-
Inspect HTTP response headers for CSRF protectionUse browser developer tools or curl to capture HTTP headers when accessing the Dashboard page. Look for the presence of anti-CSRF tokens in cookies or response headers, or for the presence of Referer header validation.Affected if No anti-CSRF token is present in cookies or form submissions, and no Referer validation is enforced.
The environment is affected if the installed version is exactly 5.4.0.46.6, 5.5.0.36, or 5.5.0.46.4 and the Dashboard monitoring-and-reporting interface is accessible without CSRF protections.
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 vendor patch version 5.5(0.46.5) or later; if immediate patching is not feasible, implement anti-CSRF tokens and Referer header validation on affected Dashboard endpoints.
Fix this in Secure Access Control Server Solution Engine
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0700 — 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-0700 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