CVE-2025-2480
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 · uneditedSantesoft Sante DICOM Viewer Pro is vulnerable to an out-of-bounds write, which requires a user to open a malicious DCM file, resulting in execution of arbitrary code by a local attacker.
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 confidenceSantesoft Sante DICOM Viewer Pro contains an out-of-bounds write vulnerability in its DCM file parsing functionality. When a user opens a specially crafted malicious DCM file, the parser writes data beyond the boundaries of an allocated buffer, allowing a local attacker to overwrite memory and execute arbitrary code with the privileges of the user running the viewer.
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< 14.2.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Verify Sante DICOM Viewer Pro is installedCheck for the presence of Sante DICOM Viewer Pro on the system by searching for the application in installed programs (Windows: Control Panel > Programs and Features, or use 'Get-ItemProperty' in PowerShell for registry entries under HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall)Affected if The application is listed as installed on the system
-
Determine installed versionLocate the installed version by checking the application's About dialog, executable file properties (right-click the executable > Properties > Details), or the uninstall registry entry which typically contains the version numberAffected if The version number returned is lower than 14.2.0 (for example, 14.1.x, 14.0.x, or earlier)
-
Confirm DCM file handling capabilityVerify the application can process DCM files by checking if the file association for .dcm files is registered to Sante DICOM Viewer Pro, or by attempting to open a DCM file through the applicationAffected if DCM files are associated with or can be opened by Sante DICOM Viewer Pro
A user is affected if Sante DICOM Viewer Pro version 14.2.0 or later is NOT installed and the application can open DCM files.
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 · scoped14.2.0
Organizations should exercise caution when opening DCM files from untrusted sources, implement email filtering for DCM attachments, and monitor for updates from Santesoft that address this vulnerability.
14.2.0
- Upgrade Santesoft Sante DICOM Viewer Pro to version 14.2.0 or later to remediate the out-of-bounds write vulnerability (CVE-2025-2480).
- Obtain the updated installer from the official Santesoft website (santesoft.com) or your licensed download channel.
- Close any running instances of Sante DICOM Viewer Pro.
- Run the installer for version 14.2.0 or later and follow the installation prompts.
- After installation, verify the installed version matches 14.2.0 or higher.
- Exercise caution when opening DCM files from untrusted sources, as the attack vector involves opening malicious DCM files.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2480 — 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-2480 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