# CVE-2024-1696: Santesoft Sante FFT Imaging Out-of-bounds Write

> A local attacker can execute arbitrary code by tricking a user into opening a malicious DCM file in Sante FFT Imaging.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Mar 2024
- **Updated:** 12 Aug 2024
- **Also known as:** GHSA-4g86-mfr6-26v9

## What is CVE-2024-1696?

CVE-2024-1696 is a high-severity memory corruption vulnerability in Santesoft Sante FFT Imaging, published on 11 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In Santesoft Sante FFT Imaging versions 1.4.1 and prior once a user opens a malicious DCM file on affected FFT Imaging installations, a local attacker could perform an out-of-bounds write, which could allow for arbitrary code execution.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-1696?

It affects 1 product.


Products: Santesoft Fft Imaging.

## How do I fix CVE-2024-1696?

No fix has been published for CVE-2024-1696 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-1696 being exploited?

There is no known exploitation of CVE-2024-1696 in the wild and no public exploit code.

## Other vulnerabilities in Santesoft Sante FFT Imaging

- [CVE-2023-5059](https://insights.sbomify.com/CVE-2023-5059/): Santesoft Sante FFT Imaging Out-of-bounds Read (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1696 and fix it if it is affected.

What it is: CVE-2024-1696 is a high-severity memory corruption vulnerability in Santesoft Sante FFT Imaging, published on 11 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-1696 in the wild and no public exploit code.

Affected product: Santesoft Sante FFT Imaging. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1696/ (Markdown: https://insights.sbomify.com/CVE-2024-1696/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1696
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1696
- OSV: https://osv.dev/vulnerability/CVE-2024-1696

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1696/
Summaries are generated and may contain mistakes; the official description above is the record.