CVE-2014-6077
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 Security Access Manager for Mobile 8.x before 8.0.1 and Security Access Manager for Web 7.x before 7.0.0 FP10 and 8.x before 8.0.1 allows remote attackers 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 · moderate confidenceCSRF vulnerability in IBM Security Access Manager allows remote attackers to hijack authenticated user sessions to inject malicious XSS sequences. The flaw affects Mobile 8.x before 8.0.1 and Web 7.x before FP10/8.x before 8.0.1.
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= 7.0= 8.0= 8.0CVSS 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 IBM Security Access Manager productCheck your installed product documentation or system inventory to determine if you have Security Access Manager for Web or Security Access Manager for Mobile installedAffected if The product is IBM Security Access Manager for Mobile 8.x or IBM Security Access Manager for Web 7.x/8.x
-
Determine the installed version numberUse the product's version detection method (such as checking the product about page, version file, or administrative console) to obtain the exact version and build numberAffected if The version is below 8.0.1 for Mobile, below 8.0.1 for Web 8.x, or below FP10 for Web 7.x
-
Compare your version to affected rangesMatch your detected version against the vulnerable ranges: Mobile 8.x before 8.0.1, Web 7.x before FP10, Web 8.x before 8.0.1Affected if Your version falls within any of these vulnerable ranges and the product is in production use with active administrative sessions
-
Verify administrative interface exposureDetermine if the administrative console is network-accessible from untrusted networks, as this CSRF vulnerability exploits authenticated admin sessionsAffected if The administrative interface is accessible and users have active authenticated sessions
You are affected if you have IBM Security Access Manager for Mobile 8.x before 8.0.1, or Web 7.x before FP10, or Web 8.x before 8.0.1, and the admin interface is in use.
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 IBM Security Access Manager patches: upgrade Mobile to 8.0.1+, Web 7.x to FP10+, and Web 8.x to 8.0.1+. Verify all admin sessions are invalidated after patching.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6077 — 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-6077 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