dbcve.org
Sante Pacs ServerApplication · Santesoft

CVE-2025-0571

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

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

Sante PACS Server Web Portal contains a memory corruption vulnerability in its DCM file parsing functionality. The lack of proper validation of user-supplied data during DCM file parsing allows an authenticated attacker to cause memory corruption, resulting in a denial-of-service condition.

MitigationRestrict access to the Web Portal to only authenticated, authorized users; apply vendor patches when available; implement input validation and bounds checking on DCM file parsing routines.

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. Verify Sante PACS Server version
    Locate the installed Sante PACS Server software and check its version number. Common locations include the program files directory, the server administration interface, or by querying the service information. Compare the installed version against the affected range: versions prior to 4.0.10 are vulnerable.
    Affected if The installed version is lower than 4.0.10
  2. Confirm Web Portal is enabled
    Check if the Sante PACS Server Web Portal service is running and accessible. This is typically accessible via HTTP/HTTPS on a configured port (commonly 8000 or 8080). Verify the portal responds to requests.
    Affected if The Web Portal is running and accessible
  3. Verify authentication is required for portal access
    Inspect the Web Portal configuration to confirm that authentication is enforced for all users. Attempt to access the portal without credentials or check the authentication settings in the server configuration.
    Affected if The Web Portal allows unauthenticated access to its DCM file parsing functionality
  4. Confirm DCM file upload or parsing feature is active
    Determine if the Web Portal includes DCM file upload, viewing, or parsing capabilities. This is typically part of DICOM image management features. Check if this module is loaded and operational within the portal.
    Affected if DCM file parsing functionality is available through the Web Portal without additional restrictions

A system is affected if it runs Sante PACS Server version lower than 4.0.10 AND has the Web Portal exposed with DCM file parsing capabilities accessible to users.

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

Restrict access to the Web Portal to only authenticated, authorized users; apply vendor patches when available; implement input validation and bounds checking on DCM file parsing routines.

Recommended fix High confidence

4.0.10 or later

  1. Verify current Sante PACS Server version by accessing the web portal or checking system information
  2. Create a complete backup of the database, configuration files, and any custom settings
  3. Download Sante PACS Server version 4.0.10 or later from the official vendor source
  4. Stop the Sante PACS Server service before applying the update
  5. Install the upgraded version (4.0.10 or later) following vendor documentation
  6. Restart the Sante PACS Server service
  7. Verify the web portal is accessible and the DCM file parsing functionality works correctly
  8. Confirm the version number has been updated post-upgrade

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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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