CVE-2020-14484
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 · uneditedOpenClinic GA versions 5.09.02 and 5.89.05b may allow an attacker to bypass the system’s account lockout protection, which may allow brute force password attacks.
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 confidenceOpenClinic GA versions 5.09.02 and 5.89.05b contain an authentication flaw that allows attackers to circumvent the built-in account lockout mechanism. This enables unlimited brute force password attempts against user accounts, leading to complete account compromise.
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.09.02= 5.89.05bCVSS 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.1/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 the installed OpenClinic GA versionCheck the application's version information through the admin interface, footer of pages, or version file in the installation directory. Common locations include: the about page, a version info file, or the application banner on login pages.Affected if The installed version matches 5.09.02 or 5.89.05b exactly
-
Verify network accessibility of the login pageConfirm the OpenClinic GA web interface is accessible over the network. Check if port 80/443 or the configured HTTP port is listening and reachable from untrusted networks.Affected if The login page is exposed to network access, allowing external attackers to attempt the brute force attack
-
Confirm account lockout is configuredReview the application's security settings for account lockout configuration. This is typically found in the admin panel under security, authentication, or user management settings.Affected if Account lockout is enabled but can be bypassed through the authentication flaw (the vulnerable versions have a bypass vulnerability regardless of lockout settings)
-
Check for failed login attempt logsReview application logs or audit logs for patterns of repeated failed login attempts against user accounts that did not trigger lockout.Affected if Logs show numerous failed login attempts against the same account without lockout being triggered, indicating the bypass is being exploited
You are affected if OpenClinic GA version 5.09.02 or 5.89.05b is installed and the login interface is network-accessible, as the account lockout mechanism can be bypassed in these versions.
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 proper server-side enforcement of account lockout after failed login attempts, ensuring the lockout cannot be bypassed through the discovered attack vector.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14484 — 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-14484 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