dbcve.org
Openclinic GaApplication · Openclinic Ga Project

CVE-2023-40275

CRITICAL · 9.1 CVSS v3.1 Published 2024-03-19
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
An issue was discovered in OpenClinic GA 5.247.01. It allows retrieval of patient lists via queries such as findFirstname= to _common/search/searchByAjax/patientslistShow.jsp.

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 5.247.01 contains an unauthenticated information disclosure vulnerability in the /_common/search/searchByAjax/patientslistShow.jsp endpoint. Attackers can retrieve sensitive patient data including names and other PII/PHI by sending queries with the findFirstname parameter without any authentication, posing severe HIPAA compliance violations.

MitigationImplement proper authentication and role-based authorization checks on the patient search endpoint to ensure only authorized medical personnel can access patient lists. Validate that requests originate from authenticated sessions with appropriate clinical access permissions.

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.247.01

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

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

  1. Confirm OpenClinic GA installation
    Locate the OpenClinic GA web application directory or check running services on the host. Look for the typical installation path (e.g., /var/www/openclinic, C:\inetpub\openclinic, or within a Java application server like Tomcat).
    Affected if OpenClinic GA is not installed on the system.
  2. Verify the installed version
    Check the version file or manifest within the OpenClinic GA installation. Common locations include a version.txt file, the WAR file name, or the pom.xml/build.properties if source is available. The affected version is exactly 5.247.01.
    Affected if The installed version is 5.247.01.
  3. Confirm the vulnerable endpoint exists
    Check if the file patientslistShow.jsp exists under the /_common/search/searchByAjax/ directory within the web application root. Inspect the web.xml deployment descriptor to confirm the URL pattern /_common/search/searchByAjax/ is mapped.
    Affected if The endpoint file exists and is accessible via the web application.
  4. Verify the findFirstname parameter is accepted without authentication
    Review the patientslistShow.jsp source code to determine whether any authentication checks (session validation, role verification) are performed before processing the findFirstname parameter. Look for include statements to auth checks or session validation logic at the top of the file.
    Affected if The JSP processes the findFirstname parameter without requiring a valid authenticated session.
  5. Test endpoint accessibility externally
    Using a browser or HTTP client, attempt to access the endpoint URL with a findFirstname parameter (e.g., /_common/search/searchByAjax/patientslistShow.jsp?findFirstname=Test) without providing any session cookies or authentication headers.
    Affected if The endpoint returns patient data or list results without requiring authentication credentials.

A user is affected if OpenClinic GA version 5.247.01 is installed and the /_common/search/searchByAjax/patientslistShow.jsp endpoint accepts the findFirstname parameter without requiring authenticated session credentials, allowing unauthorized access to patient PII/PHI data.

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 proper authentication and role-based authorization checks on the patient search endpoint to ensure only authorized medical personnel can access patient lists. Validate that requests originate from authenticated sessions with appropriate clinical access permissions.

Recommended fix Moderate confidence

Latest stable OpenClinic GA version ( newer than 5.247.01 )

  1. 1. Navigate to the official OpenClinic GA download page at sourceforge.net/projects/open-clinic/ or the GitHub repository.
  2. 2. Download the latest stable release version ( newer than 5.247.01 ).
  3. 3. Back up the existing OpenClinic GA database and application files.
  4. 4. Deploy the new version following the standard upgrade procedure for OpenClinic GA.
  5. 5. Verify that the /_common/search/searchByAjax/patientslistShow.jsp endpoint now requires proper authentication.
  6. 6. Test that patient data is no longer accessible without valid authentication credentials.
Caveat Minor version upgrades typically maintain backward compatibility but always review release notes

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

Fix this in Openclinic Ga Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40275 — 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-2023-40275 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