dbcve.org
Sante Pacs ServerApplication · Santesoft

CVE-2025-0573

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-30
Fix available
A fix is available. Upgrade to 4.0.10 or later.
See remediation →
62/100
Remediation priority · Elevated
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 DCM File Parsing Directory Traversal Arbitrary File Write Vulnerability. This vulnerability allows remote attackers to create arbitrary files on affected installations of Sante PACS Server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the parsing of DCM files. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to write files in the context of the current user. Was ZDI-CAN-25309.

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

Sante PACS Server suffers from a directory traversal vulnerability in its DCM file parsing functionality. The application fails to validate user-supplied paths before performing file operations, allowing remote unauthenticated attackers to write arbitrary files to the filesystem by embedding path traversal sequences (e.g., ../) in specially crafted DCM files.

MitigationApply vendor patch when available. In the interim, restrict file write permissions on the application service account and implement network segmentation to limit exposure. Consider validating DCM files through a sandbox before processing.

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:< 4.0.10

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
None
Integrity
Low
Availability
None

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

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

  1. Confirm Sante PACS Server installation
    Check for the presence of Sante PACS Server software on the system - look for installation directories (commonly under C:\Program Files\Santesoft or similar) or check Windows Programs and Features for 'Sante PACS Server'.
    Affected if Sante PACS Server is installed on the system
  2. Identify installed version
    Locate the installed executable (usually named something like SantePacsServer.exe or within a versioned folder) and check its file properties for version information, or query the application via its built-in about/version functionality if available.
    Affected if The installed version is lower than 4.0.10 (e.g., 4.0.9, 4.0.8, etc.)
  3. Verify DCM file processing is enabled
    Check if the DICOM (DCM) receiving/storage functionality is configured and active - look for incoming DICOM storage directories, DICOM listener services, or web endpoints that accept DCM file uploads.
    Affected if The DCM file reception or storage service is enabled and accessible
  4. Assess network exposure
    Determine if the PACS server is listening on network interfaces and accessible from outside trusted networks - check firewall rules, binding addresses, and whether the service port (typically 104, 11112, or HTTP ports) is exposed externally.
    Affected if The PACS server is accessible from untrusted networks or the internet

You are affected if Sante PACS Server version is below 4.0.10 AND the DCM file processing/reception feature is enabled and accessible.

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 4.0.10 or later
Fixed in 4.0.10
Interim mitigation

Apply vendor patch when available. In the interim, restrict file write permissions on the application service account and implement network segmentation to limit exposure. Consider validating DCM files through a sandbox before processing.

Recommended fix High confidence

Sante PACS Server 4.0.10

  1. Obtain Sante PACS Server version 4.0.10 or later from the official vendor (Sante or authorized distributor)
  2. Review release notes and migration guide for version 4.0.10
  3. Create a complete backup of the current Sante PACS Server installation including database and configuration files
  4. Stop the Sante PACS Server service
  5. Install version 4.0.10 using the vendor's documented upgrade procedure
  6. Verify file permissions and configuration settings are correctly applied after upgrade
  7. Restart the Sante PACS Server service
  8. Validate that DCM file parsing functionality operates normally

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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