dbcve.org
Openclinic GaApplication · Openclinic Ga Project

CVE-2020-14485

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
OpenClinic GA versions 5.09.02 and 5.89.05b may allow an attacker to bypass client-side access controls or use a crafted request to initiate a session with limited functionality, which may allow execution of admin functions such as SQL queries.

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 confidence

OpenClinic GA versions 5.09.02 and 5.89.05b contains a critical access control bypass vulnerability where client-side security checks can be circumvented. Attackers can craft malicious requests to initiate sessions with elevated privileges, bypassing intended session limitations. This enables unauthorized execution of administrative functions including SQL queries, indicating potential SQL injection or direct admin API access.

MitigationImplement robust server-side access control enforcement on all sensitive endpoints, eliminate reliance on client-side controls for security decisions, and add proper authentication/authorization validation before executing admin functions or database queries.

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
Openclinic GaApplication
Affected:= 5.09.02= 5.89.05b

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate OpenClinic GA installation
    Search the web server document root for openclinic files, typically in a directory named 'openclinic' or similar. Look for the characteristic directory structure containing jsp files and the WEB-INF folder.
    Affected if OpenClinic GA is installed on the server
  2. Identify installed version
    Check for a version file in the installation directory, or access the application's main page and look for a version display. Common locations include a version.properties file or the about/admin page.
    Affected if The installed version matches 5.09.02 or 5.89.05b exactly
  3. Verify administrative functions exist
    Examine the application for admin-level features such as database query tools, user management panels, or system configuration pages accessible through the web interface.
    Affected if Administrative or database query functions are present in the application
  4. Confirm application processes user requests
    Review the application's request handling code to determine if it relies on client-side validation (javascript checks, hidden form fields, or client-side cookies) for security decisions before executing sensitive operations.
    Affected if The application uses client-side mechanisms for access control that could be bypassed

A user is affected if OpenClinic GA versions 5.09.02 or 5.89.05b are installed and the application relies on client-side security checks that can be circumvented by an attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust server-side access control enforcement on all sensitive endpoints, eliminate reliance on client-side controls for security decisions, and add proper authentication/authorization validation before executing admin functions or database queries.

Recommended fix Moderate confidence

Latest stable release of OpenClinic GA (newer than 5.89.05b)

  1. 1. Identify the current OpenClinic GA version in use by accessing the application's admin interface or checking the deployed files.
  2. 2. If running version 5.09.02 or 5.89.05b, backup the entire database and application files before any upgrade.
  3. 3. Obtain the latest stable release of OpenClinic GA from the official source (openclinic.sourceforge.net).
  4. 4. Deploy the latest version following the standard upgrade procedures documented for OpenClinic GA.
  5. 5. Verify that client-side access controls are no longer present as the sole validation mechanism - server-side validation should be enforced.
  6. 6. Test that authentication and authorization mechanisms properly restrict access to admin functions and SQL query interfaces.
  7. 7. Confirm the SQL injection/execution vulnerability is remediated by attempting authorized admin operations only.
Caveat Review release notes for the target version to check for database schema changes that may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclinic Ga Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA8.0 h
40.0 hours of engineering $7,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14485 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14485 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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