CVE-2014-6087
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 · uneditedIBM 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 make it easier for remote attackers to obtain sensitive information by sniffing the network during use of a weak algorithm in an SSL cipher suite.
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 confidenceIBM Security Access Manager for Mobile and Web versions use weak SSL cipher suites containing weak cryptographic algorithms, allowing remote attackers to sniff network traffic and obtain sensitive information by exploiting these weak ciphers.
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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Security Access Manager productLocate the IBM Security Access Manager installation and determine whether it is the Web or Mobile variant. Check the product name displayed in the management console or installed programs list.Affected if The product is IBM Security Access Manager for Web or IBM Security Access Manager for Mobile
-
Check installed product versionUse the product's management interface or command-line tool to query the exact version number installed. Compare this version against the affected ranges: ISAM for Web versions 7.0 and 8.0, ISAM for Mobile version 8.0.Affected if The installed version is exactly 7.0 or 8.0 for ISAM for Web, or exactly 8.0 for ISAM for Mobile
-
Locate SSL/TLS configuration settingsAccess the product administration interface or configuration files where SSL cipher suites are defined. Look for sections controlling SSL/TLS negotiation settings.Affected if Weak cipher suites are configurable in the product's SSL settings
-
Inspect enabled cipher suitesReview the list of SSL cipher suites currently enabled. Identify any ciphers using weak algorithms such as export-grade encryption, DES, 3DES, RC4, or MD5 hash functions.Affected if Any weak or export-grade cipher suites are enabled in the SSL configuration
-
Verify cipher suite strength policyCheck whether the product has a policy enforcing strong cipher suites only, or if weak ciphers are permitted in the current configuration.Affected if The configuration allows weak cipher suites or does not enforce strong ciphers only
A user is affected if IBM Security Access Manager for Web (7.0 or 8.0) or for Mobile (8.0) is installed with weak SSL cipher suites enabled in the configuration.
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 dataUpgrade to IBM Security Access Manager for Mobile 8.0.1+, Web 7.0.0 FP10+, or Web 8.0.1+, or reconfigure the product to use strong SSL cipher suites only.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6087 — 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-6087 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