CVE-2017-9393
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 · uneditedCA Identity Manager r12.6 to r12.6 SP8, 14.0, and 14.1 allows remote attackers to potentially identify passwords of locked accounts through an exhaustive search.
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 confidenceCA Identity Manager versions r12.6 through r12.6 SP8, 14.0, and 14.1 contains an authentication enumeration vulnerability where the application responds differently to login attempts with locked accounts versus invalid credentials, allowing remote attackers to conduct exhaustive search attacks to discover passwords of locked 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= 12.6= 14.0= 14.1= 14.0= 14.1CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 CA Identity Manager versionLocate the installation directory and check the version file or use the product's built-in version check utility (typically found in the admin console or via ims.Version property)Affected if Installed version is 12.6 through 12.6 SP8, 14.0, or 14.1 (or Virtual Appliance versions 14.0/14.1)
-
Confirm authentication endpoint is network-accessibleVerify that the CA Identity Manager login portal or API endpoint is exposed to network access rather than being fully internal-onlyAffected if The authentication interface is reachable from network locations where attackers could conduct enumeration attacks
-
Test authentication response for locked accountAttempt a login with a known locked or disabled user account and capture the HTTP response code and messageAffected if Response differs from invalid credential response (e.g., returns 'account locked' versus 'invalid credentials' message)
-
Test authentication response for invalid credentialsAttempt a login with a clearly invalid username and/or password and capture the HTTP response code and messageAffected if Response differs from locked account response, revealing which usernames are valid
-
Verify absence of response normalizationCompare server responses across multiple authentication scenarios including valid user with wrong password, invalid user, locked user, and disabled userAffected if Any distinguishable difference in error messages or HTTP status codes reveals account validity to attackers
User is affected if running an affected version (12.6-12.6 SP8, 14.0, or 14.1) AND the authentication endpoint is network-accessible AND the application returns distinguishable responses between locked accounts and invalid credentials.
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 patch from CA/Broadcom. As an interim control, implement rate-limiting or IP-based restrictions on authentication endpoints to limit brute force attempts, and ensure monitoring alerts fire on excessive failed authentication attempts against the same account.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9393 — 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-2017-9393 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