dbcve.org
Sante Pacs ServerApplication · Santesoft

CVE-2025-0570

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-30
Fix available
A fix is available. Upgrade to 4.0.10 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Web Portal 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 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-25304.

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

Memory corruption vulnerability in Sante PACS Server Web Portal during DCM (DICOM) file parsing. The lack of proper validation of user-supplied data during DCM file processing allows an authenticated attacker to trigger memory corruption, resulting in denial-of-service.

MitigationApply vendor-supplied patches for Sante PACS Server when available. Until then, restrict administrative access to the web portal, implement strict input validation on uploaded DCM files, and monitor for anomalous parsing behavior.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Sante PACS Server installation
    Locate the Sante PACS Server application in your environment. Check for processes named 'SantePacsServer', 'Sante PACS Server', or look in typical installation directories such as C:\Program Files\Santesoft\ or /opt/santesoft/. Identify the executable or service responsible for the PACS server.
    Affected if The software is not found or is a different product entirely.
  2. Check installed version
    Open the Sante PACS Server management console, check the About/Help section, or run 'SantePacsServer.exe -v' from the installation directory. Compare the version number to the affected range: any version below 4.0.10 is vulnerable.
    Affected if The installed version is lower than 4.0.10.
  3. Verify web portal is enabled
    Check the Sante PACS Server configuration for web portal settings. Look for HTTP/HTTPS listener configuration, typically in the server configuration file or management interface. Confirm the web portal service is running and accessible via browser.
    Affected if The web portal interface is exposed and accessible.
  4. Confirm DCM file processing is active
    Inspect the Sante PACS Server configuration for DICOM (DCM) storage or processing services. Check if the DICOM listener and DCM file import/processing feature are enabled in the server settings or services panel.
    Affected if DCM file parsing or DICOM storage services are enabled on the server.
  5. Review authentication configuration
    Examine the web portal authentication settings in the Sante PACS Server administration panel. Verify whether user accounts exist and authentication is required for portal access, as the CVE requires an authenticated attacker.
    Affected if Web portal authentication is configured and user accounts are active.

You are affected if Sante PACS Server version is below 4.0.10 AND the web portal with DCM file processing is accessible, regardless of authentication status since the vulnerability becomes exploitable once these conditions are met.

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-supplied patches for Sante PACS Server when available. Until then, restrict administrative access to the web portal, implement strict input validation on uploaded DCM files, and monitor for anomalous parsing behavior.

Recommended fix Moderate confidence

4.0.10 or later

  1. Identify the current installed version of Sante PACS Server
  2. Download Sante PACS Server version 4.0.10 or later from the official vendor website
  3. Apply the upgrade following the vendor's standard upgrade procedure
  4. Verify the upgrade was successful and the service is running properly

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

Fix this in Sante Pacs Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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