Unified Intelligence CenterApplication · Cisco
CVE-2015-0740
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 Cisco Unified Intelligence Center 10.6(1) allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCus28826.
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 confidenceCross-site request forgery (CSRF) vulnerability in Cisco Unified Intelligence Center version 10.6(1) allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into submitting 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
Unified Intelligence CenterApplication
= 10.6\(1\)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
- 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 installed Cisco Unified Intelligence Center versionAccess the application's admin interface or use the system inventory tool to retrieve the exact version number. Typically found in Help > About or System Administration > Version Information.Affected if The installed version is exactly 10.6(1)
-
Confirm web interface is accessibleVerify that the Cisco Unified Intelligence Center web interface is reachable and operational by accessing the login page via HTTPS.Affected if The web interface is exposed and the version is 10.6(1)
-
Inspect form submissions for CSRF tokensLog into the application and navigate to a state-changing operation (such as creating a report, modifying user settings, or changing configurations). View the HTML source or intercept the request to check if a unique token parameter is included with each POST request.Affected if No anti-CSRF token parameter is present in state-changing forms and the version is 10.6(1)
-
Check request header validationUsing a browser developer tool or HTTP proxy, observe whether the application validates the Origin or Referer headers on POST requests. Submit a request from an external domain and check if it is accepted or rejected.Affected if The application accepts state-changing requests without validating Origin or Referer headers and the version is 10.6(1)
You are affected if running exactly version 10.6(1) of Cisco Unified Intelligence Center and the application lacks anti-CSRF tokens or Origin/Referer header validation for state-changing operations.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations and validate the Origin or Referer headers. For Cisco Unified Intelligence Center, apply the vendor patch for Bug ID CSCus28826.
Fix this in Unified Intelligence Center
Scoped from the published advisory
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0740 — 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-0740 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