CVE-2014-0961
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 IBM Tivoli Identity Manager (ITIM) 5.0 before 5.0.0.15 and 5.1 before 5.1.0.15 and IBM Security Identity Manager (ISIM) 6.0 before 6.0.0.2 allows remote authenticated users to hijack the authentication of arbitrary users for requests that insert XSS sequences.
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 confidenceCSRF vulnerability in IBM ITIM/ISIM allows authenticated remote users to hijack authentication of arbitrary users for requests that insert XSS sequences. The flaw exists in versions prior to ITIM 5.0.0.15/5.1.0.15 and ISIM 6.0.0.2, enabling attackers to craft malicious requests that bypass Same-Origin Policy protections.
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= 6.0.0= 6.0.0.1= 5.0.0= 5.0.0.6= 5.0.0.10= 5.0.0.11= 5.0.0.12= 5.0.0.13= 5.0.0.14= 5.1.0= 5.1.0.3= 5.1.0.4= 5.1.0.5= 5.1.0.6CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 IBM ITIM/ISIM versionLocate the version file or about page in the IBM Identity Manager installation. Common paths include the 'about' page at /itim/console or checking version.info in the installation directory. Alternatively, access the administrative console and navigate to the 'About' or 'Version Information' section.Affected if The displayed version matches one of these: ITIM 5.0.0 through 5.0.0.14, ITIM 5.1.0 through 5.1.0.6, ISIM 6.0.0 or 6.0.0.1
-
Confirm web interface is enabledVerify that the IBM ITIM/ISIM web console is accessible. Check if the HTTP/HTTPS ports configured for the ITIM/ISIM web application are listening and responding. Look for the login page at the configured ITIM endpoint.Affected if The web interface is exposed and accessible to users or attackers on the network
-
Check for missing CSRF protectionInspect HTTP responses from the ITIM/ISIM web application for anti-CSRF tokens or SameSite cookie attributes. Examine the Set-Cookie headers and form submissions within the application for the presence of token-based CSRF mitigations.Affected if No anti-CSRF tokens are found in forms and no SameSite attributes are set on session cookies
Your environment is affected if the installed IBM Tivoli Identity Manager version is 5.0.0 through 5.0.0.14, 5.1.0 through 5.1.0.6, or IBM Security Identity Manager is 6.0.0/6.0.0.1 and the web interface is enabled 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 patches (ITIM 5.0.0.15+, 5.1.0.15+, ISIM 6.0.0.2+) to address the CSRF vulnerability; implement anti-CSRF tokens and SameSite cookie attributes as defense-in-depth.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0961 — 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-2014-0961 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