CVE-2014-6078
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 do not have a lockout period after invalid login attempts, which makes it easier for remote attackers to obtain admin access via a brute-force attack.
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 8.x before 8.0.1 and Security Access Manager for Web 7.x/8.x before specified patch levels lack account lockout functionality after failed login attempts, enabling remote attackers to conduct brute-force attacks against admin accounts.
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= 8.0= 7.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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 the installed IBM Security Access Manager product and versionLocate the ISAM installation directory and check the version file, or run the product version command (typically 'version' or check /opt/IBM/ISAM/installed.xml or similar product-specific version file)Affected if The installed version is ISAM Mobile 8.0 or ISAM Web 7.0/8.0 without the corresponding fixed patch levels (Mobile 8.0.1, Web 7.0 FP10, Web 8.0.1)
-
Check if account lockout policy is configured in authentication settingsAccess the ISAM admin console or configuration files and navigate to Authentication > Policy > Account Lockout. Verify whether an account lockout threshold is defined.Affected if No account lockout threshold is set or the lockout feature is disabled/zero
-
Verify the brute-force protection configurationReview the authentication configuration XML or JSON files (commonly found in /var/isd/amp/config/ or similar config directory) for 'maxFailedAttempts' or 'lockoutDuration' parametersAffected if The maxFailedAttempts parameter is missing, set to 0, or not present in the authentication policy
-
Confirm admin account password policy settingsCheck the administrator user registry or LDAP configuration for account lockout attributes. In the admin console, go to User Registry > Administrators > Account Lockout settings.Affected if Account lockout settings are not defined or are set to unlimited failed attempts
A user is affected if they are running a vulnerable version (ISAM Mobile 8.0, Web 7.0, or Web 8.0 without patches) AND account lockout is not configured in the authentication policy.
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 (ISAM Mobile 8.0.1, Web 7.0.0 FP10, Web 8.0.1) or implement temporary account lockout policies with appropriate threshold and duration settings in the authentication configuration.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6078 — 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-6078 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