dbcve.org
Fft ImagingApplication · Santesoft

CVE-2023-5059

HIGH · 7.8 CVSS v3.1 Published 2023-10-19
Fix available
A fix is available. Upgrade to 1.4.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Santesoft Sante FFT Imaging lacks proper validation of user-supplied data when parsing DICOM files. This could lead to an out-of-bounds read. An attacker could leverage this vulnerability to execute arbitrary code in the context of the current process.

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

Santesoft Sante FFT Imaging contains a vulnerability due to insufficient validation of user-controlled data during DICOM file parsing. This improper validation results in an out-of-bounds read condition that can be triggered by a specially crafted DICOM file. Successful exploitation allows an attacker to achieve arbitrary code execution within the context of the running process.

MitigationRestrict processing to trusted DICOM files from known sources, and apply any vendor-supplied patches when available. Consider deploying additional file sanitization or sandboxing for DICOM processing until a fix is implemented.

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
Fft ImagingApplication
Affected:< 1.4.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Sante FFT Imaging is installed
    Check for the application in the system program files directory or use system inventory tools to find Sante FFT Imaging. Look for executable files named 'Sante FFT Imaging' or similar Sante-related imaging software.
    Affected if The software is present on the system
  2. Determine installed version
    Open the application and navigate to Help > About, or right-click the executable file and view Properties > Details to see the version number. Compare against the vulnerable range: versions prior to 1.4.1.
    Affected if The installed version is below 1.4.1
  3. Identify DICOM processing capability
    Check if the application has DICOM file import or parsing features enabled. Look for menu options like 'Import DICOM', 'Open DICOM', or file associations with .dcm extensions.
    Affected if DICOM file import/parsing features are available and enabled
  4. Review DICOM file handling behavior
    Monitor the application when processing DICOM files using process monitoring tools. Observe if the application reads file content without proper bounds checking, which may manifest as unusual memory access patterns.
    Affected if The application processes DICOM files from external or untrusted sources

The environment is affected if Sante FFT Imaging version 1.4.1 or lower is installed and the system processes DICOM files with this software.

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 1.4.1 or later
Fixed in 1.4.1
Interim mitigation

Restrict processing to trusted DICOM files from known sources, and apply any vendor-supplied patches when available. Consider deploying additional file sanitization or sandboxing for DICOM processing until a fix is implemented.

Recommended fix High confidence

1.4.1

  1. Identify the current version of Santesoft Sante FFT Imaging installed
  2. Download Santesoft Sante FFT Imaging version 1.4.1 or later from the official Santesoft vendor website
  3. Backup any existing DICOM files and application data before upgrading
  4. Install the updated version following the vendor's installation instructions
  5. Verify the installation was successful and the version is 1.4.1 or higher

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

Fix this in Fft Imaging Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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