CVE-2025-0568
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 · uneditedSante 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-25302.
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 confidenceSante PACS Server contains a memory corruption vulnerability in its DCM file parser due to insufficient validation of user-supplied data. An unauthenticated remote attacker can send specially crafted DCM files to trigger the memory corruption, resulting in denial of service. The vulnerability stems from the lack of proper bounds checking or input sanitization during the parsing process.
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< 4.0.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Sante PACS Server is installedCheck for the Sante PACS Server installation directory (commonly in Program Files or Program Files (x86) under Santesoft), or look for the service running on standard DICOM ports (usually 104, 11112, or as configured)Affected if The software is installed and running on the system
-
Determine the installed versionCheck the version of Sante PACS Server - typically found in the application's About dialog, in the installation directory's version info, or in Windows Registry under the application's uninstall entryAffected if The version number is lower than 4.0.10 (e.g., 4.0.9, 4.0.8, etc.)
-
Verify the DCM parser service is network-accessibleCheck if the DICOM listener/service is bound to a network interface and accepting connections - verify the service is listening on the configured DICOM port (default often 104 or 11112) and accessible from network hostsAffected if The PACS server is listening on a reachable network interface and accepts remote connections
-
Confirm DCM file import/processing is enabledVerify that the DICOM storage (C-STORE SCP) functionality is enabled and configured to accept DCM files from remote clients - check the server configuration for allowed incoming association issuers or storage commitment settingsAffected if The server is configured to accept DCM files from unauthenticated or remote clients
A user is affected if Sante PACS Server is installed with a version below 4.0.10 and the DICOM service is network-accessible and configured to accept incoming DCM files from remote clients.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.0.10
Apply the vendor patch or update Sante PACS Server to the latest version that addresses this vulnerability. Until patched, consider restricting network access to the PACS server and implementing additional input validation at network boundaries.
Sante PACS Server 4.0.10 or later
- 1. Identify the current version of Sante PACS Server installed in your environment
- 2. Download Sante PACS Server version 4.0.10 or later from the official vendor website or your licensed distribution channel
- 3. Review the vendor's upgrade documentation and release notes for version 4.0.10
- 4. Create a complete backup of the current Sante PACS Server installation, including all configuration files, databases, and DCM data
- 5. Test the upgrade in a non-production environment first to verify functionality
- 6. Schedule a maintenance window since the service will need to be restarted
- 7. Stop the Sante PACS Server service before applying the upgrade
- 8. Apply the version 4.0.10 upgrade following the vendor's documented procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0568 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0568 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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