CVE-2020-7962
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 · uneditedAn issue was discovered in One Identity Password Manager 5.8. An attacker could enumerate valid answers for a user. It is possible for an attacker to detect a valid answer based on the HTTP response content, and reuse this answer later for a password reset on a chosen password. The enumeration is possible because, within the HTTP response content, WRONG ID is only returned when the answer is incorrect.
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 confidenceOne Identity Password Manager 5.8 contains an insecure direct object reference in its password reset mechanism that allows answer enumeration. The application reveals whether a security question answer is correct by returning 'WRONG ID' in the HTTP response content when the answer is incorrect, enabling attackers to brute-force valid answers through repeated password reset attempts.
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= 5.8CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm installed versionCheck the One Identity Password Manager version installed in your environment. This can typically be found in the application itself under Help > About, or in the Windows Programs and Features list, or by querying the installed software inventory.Affected if The installed version is exactly 5.8 (version 5.8.0)
-
Locate password reset endpointIdentify the URL path used for the password reset / security question answer verification functionality. This is typically accessible via the web login page through a 'Forgot Password' or similar link.Affected if The password reset mechanism is exposed and accessible to unauthenticated users
-
Test for differential responseSubmit a password reset request with a known username and an incorrect security question answer. Capture the HTTP response body and examine it for the exact string 'WRONG ID'.Affected if The HTTP response contains 'WRONG ID' (or similar indication) when an incorrect answer is submitted, revealing answer validity
-
Test multiple answer attemptsSubmit multiple password reset requests with different incorrect answers for the same security question. Compare the responses to see if they differ based on answer correctness.Affected if The application provides different responses for correct vs incorrect answers, enabling enumeration
-
Check for rate limitingObserve whether the application implements any rate limiting, throttling, or account lockout after multiple password reset attempts from the same source.Affected if No rate limiting or account lockout is enforced, allowing automated brute-force attacks
You are affected if One Identity Password Manager version 5.8 is installed and the password reset mechanism returns distinguishable responses (such as 'WRONG ID') that reveal whether a security question answer is correct.
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 dataReplace the differential response with a generic message that does not indicate answer correctness, implement rate limiting and account lockout to prevent automated enumeration, and consider requiring additional verification factors.
- Consultation2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7962 — 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-2020-7962 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