dbcve.org
Sante Pacs ServerApplication · Santesoft

CVE-2023-51637

CRITICAL · 9.8 CVSS v3.0 Published 2024-05-22
Fix available
A fix is available. Upgrade to 3.3.7 or later.
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
Sante PACS Server PG Patient Query SQL Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Sante PACS Server PG. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the DICOM service, which listens on TCP port 11122 by default. When parsing the NAME element of the PATIENT record, the process does not properly validate a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of NETWORK SERVICE. Was ZDI-CAN-21579.

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 confidence

SQL injection vulnerability in Sante PACS Server PG's DICOM service (TCP port 11122). The flaw exists in parsing the NAME element of PATIENT records, where user-supplied input is not properly validated before being used in SQL query construction. This allows unauthenticated remote attackers to execute arbitrary code in the context of NETWORK SERVICE.

MitigationApply vendor-supplied patch for Sante PACS Server PG immediately. Until patch is available, consider network segmentation to restrict access to port 11122 and implement WAF rules to detect SQL injection patterns.

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
Sante Pacs ServerApplication
Affected:< 3.3.7

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.0/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. Confirm Sante PACS Server installation
    Locate the Sante PACS Server installation directory or check installed programs list on the system
    Affected if Sante PACS Server is installed and the version is below 3.3.7
  2. Identify installed version
    Check the installed Sante PACS Server version through the application UI, Windows Programs and Features, or product documentation for version location
    Affected if Version is less than 3.3.7
  3. Verify DICOM service is running
    Check if the DICOM service listener is active on TCP port 11122 using 'netstat -an | findstr 11122' or similar network scanning tool
    Affected if Port 11122 is listening and accepting connections
  4. Confirm PATIENT record processing is enabled
    Verify the DICOM service is configured to accept and process PATIENT records, which is the default operational mode for a PACS server
    Affected if The DICOM service processes PATIENT records (standard PACS operation)

The system is affected if Sante PACS Server version is below 3.3.7 AND the DICOM service on port 11122 is accessible and processing PATIENT records.

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
Upgrade available Upgrade to 3.3.7 or later
Fixed in 3.3.7
Interim mitigation

Apply vendor-supplied patch for Sante PACS Server PG immediately. Until patch is available, consider network segmentation to restrict access to port 11122 and implement WAF rules to detect SQL injection patterns.

Recommended fix High confidence

Sante PACS Server 3.3.7

  1. 1. Back up the current Sante PACS Server database and configuration files
  2. 2. Download Sante PACS Server version 3.3.7 or later from the official vendor website
  3. 3. Stop the Sante PACS Server service
  4. 4. Install the updated version 3.3.7 following the vendor's standard upgrade procedure
  5. 5. Restart the Sante PACS Server service
  6. 6. Verify the DICOM service (port 11122) is running and the application functions normally
  7. 7. Test that the PATIENT query functionality works correctly after the update

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

Fix this in Sante Pacs Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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