dbcve.org
Sante Pacs ServerApplication · Santesoft

CVE-2025-0569

HIGH · 7.5 CVSS v3.1 Published 2025-01-30
Fix available
A fix is available. Upgrade to 4.0.10 or later.
See remediation →
84/100
Remediation priority · High
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 Memory Corruption Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition 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 user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-25303.

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

Memory corruption vulnerability in Sante PACS Server's DCM file parser due to insufficient validation of user-supplied data during file parsing. Remote attackers can send specially crafted DCM files to trigger the memory corruption and cause a denial-of-service condition without authentication.

MitigationApply vendor-provided patches when available. As an interim measure, implement network segmentation to restrict exposure and consider deploying input validation at perimeter controls for DCM file uploads.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify Sante PACS Server is installed
    Check for the presence of the Sante PACS Server application in your system or list running services that contain 'PACS' or 'Sante' in their name
    Affected if The application is present and running on the system
  2. Check installed version
    Open the Sante PACS Server application or check its About/Version panel to determine the exact version number installed
    Affected if The version is lower than 4.0.10 (e.g., 4.0.9, 4.0.8, etc.)
  3. Confirm DCM file processing is enabled
    Check if the DICOM (DCM) parser service is active in the PACS Server configuration or if the server accepts DCM file uploads/connections
    Affected if DCM file parsing functionality is enabled (which is the default operational mode for a PACS server)
  4. Assess network exposure
    Review firewall rules or network configuration to determine if the PACS Server DICOM port (typically port 104 or configured port) is exposed to untrusted networks or the internet
    Affected if The server's DICOM port is accessible from untrusted network segments or external IP addresses without authentication controls

You are affected if Sante PACS Server is running with a version lower than 4.0.10 and has DCM file parsing enabled, especially if the DICOM port is exposed to untrusted networks.

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-provided patches when available. As an interim measure, implement network segmentation to restrict exposure and consider deploying input validation at perimeter controls for DCM file uploads.

Recommended fix Moderate confidence

Sante PACS Server 4.0.10 or later

  1. Download Sante PACS Server version 4.0.10 or later from the official vendor website
  2. Ensure you have a complete backup of the current configuration and database
  3. Stop the Sante PACS Server service before upgrading
  4. Install version 4.0.10 or later following the vendor's standard installation procedure
  5. Restart the Sante PACS Server service after installation
  6. Verify the service is running correctly and DCM file processing is functional

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
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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