CVE-2021-36201
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 · uneditedUnder certain circumstances a CCURE Portal user could enumerate user accounts in CCURE 9000 version 2.90 and prior versions.
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 confidenceThis is an information disclosure vulnerability in CCURE 9000 version 2.90 and prior where the CCURE Portal reveals whether user accounts exist in the system, allowing attackers to enumerate valid usernames. This is typically accomplished through differences in error messages, response codes, or timing between existing and non-existing usernames.
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<= 2.90CVSS 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.
-
Identify installed CCURE 9000 firmware versionAccess the system admin panel or check the firmware/version information in the CCURE 9000 management console. The version is typically displayed in the About or System Info section of the portal.Affected if The installed version is 2.90 or any version prior to 2.90.
-
Test login page with non-existent usernameNavigate to the CCURE Portal login page and attempt to authenticate with a username that clearly does not exist in the system. Note the exact error message or response presented.Affected if The error message differs from the message shown when attempting to log in with a valid username (for example, 'Invalid username' versus 'Invalid password').
-
Test login page with valid usernameAttempt to log in using a known valid username with an incorrect password. Compare the exact wording of any error messages or HTTP response codes to those observed with a non-existent username.Affected if The system returns a different error message, response code, or behavior for valid usernames versus non-existent usernames, indicating username disclosure.
-
Test account recovery or forgot password featureUse the password recovery or account lookup function and submit both valid and invalid usernames. Observe whether the system provides different responses based on account existence.Affected if The system reveals whether an account exists through different error messages, 'user not found' versus 'instructions sent', or any other distinguishing behavior.
-
Check for timing differences in authentication responsesSubmit multiple login or password reset requests for both existing and non-existing usernames while measuring response times using a tool or script. Compare average response times between the two scenarios.Affected if Response times are significantly different between existing and non-existing usernames, allowing enumeration through timing analysis.
A defender is affected if the installed CCURE 9000 version is 2.90 or prior AND the system exhibits different responses (error messages, codes, or timing) that reveal whether specific usernames exist in the portal.
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 dataImplement uniform error responses and validation timing for login and account recovery functions to prevent username enumeration; consider rate limiting and account lockout policies.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36201 — 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-2021-36201 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