CVE-2017-8006
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 · uneditedIn EMC RSA Authentication Manager 8.2 SP1 Patch 1 and earlier, a malicious user logged into the Self-Service Console of RSA Authentication Manager as a target user can use a brute force attack to attempt to identify that user's PIN. The malicious user could potentially reset the compromised PIN to affect victim's ability to obtain access to protected resources.
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 confidenceIn EMC RSA Authentication Manager 8.2 SP1 Patch 1 and earlier, an authenticated user with access to the Self-Service Console can conduct a brute force attack to discover another user's PIN. Once identified, the attacker can reset the victim's PIN, denying the victim access to protected resources.
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.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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.
-
Determine RSA Authentication Manager versionAccess the RSA Security Console or use the version check command available in your deployment. Common methods include checking the /opt/rsa/am/server directory or using the RSA administration CLI if available.Affected if The installed version is 8.2 or earlier (any version <= 8.2).
-
Confirm Self-Service Console is enabledLog into the RSA Security Console and navigate to the Self-Service Console configuration section under Access settings. Verify whether the Self-Service Console is active and accessible to end users.Affected if The Self-Service Console is enabled and available to authenticated users.
-
Check account lockout policy configurationIn the RSA Security Console, navigate to the Authentication Manager settings and review the account lockout policy. Look for the number of failed attempts before lockout and the lockout duration.Affected if Account lockout is disabled or the failed attempt threshold is set too high (allowing multiple PIN guessing attempts), or lockout is not enforced for Self-Service Console logins.
-
Review authentication logs for brute force indicatorsAccess the RSA Authentication Manager logs, typically found in the server logs directory. Search for repeated failed PIN validation attempts targeting multiple user accounts from the same session or IP address.Affected if Logs show patterns of repeated failed PIN attempts against different user accounts, indicating someone is exploiting the PIN discovery mechanism.
You are affected if your RSA Authentication Manager version is 8.2 or earlier AND the Self-Service Console is enabled, particularly if account lockout is not enforced for Self-Service Console PIN operations.
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 the vendor patch for RSA Authentication Manager. Additionally, implement account lockout policies and monitoring for repeated failed authentication attempts in the Self-Service Console.
- 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-2017-8006 — 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-8006 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