# CVE-2025-2357: DCMTK dcmjpls JPEG-LS Decoder memory corruption

> Remote attackers can trigger memory corruption in the DCMTK JPEG-LS decoder, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Mar 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-2357, GHSA-vwr6-5rc9-p4cw, MGASA-2025-0117, UBUNTU-CVE-2025-2357, openSUSE-SU-2025:14901-1

## What is CVE-2025-2357?

CVE-2025-2357 is a medium-severity memory corruption vulnerability in DCMTK, published on 17 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in DCMTK 3.6.9. It has been declared as critical. This vulnerability affects unknown code of the component dcmjpls JPEG-LS Decoder. The manipulation leads to memory corruption. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 3239a7915. It is recommended to apply a patch to fix this issue.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-2357?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dcmtk` | openSUSE:Tumbleweed | All versions | 3.6.9-3.1 |

Products: Offis Dcmtk.

## How do I fix CVE-2025-2357?

Apply the vendor's patch.

## Is CVE-2025-2357 being exploited?

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

## Other vulnerabilities in DCMTK

- [CVE-2024-47796](https://insights.sbomify.com/CVE-2024-47796/): Memory corruption in DCMTK (high 8.4)
- [CVE-2024-52333](https://insights.sbomify.com/CVE-2024-52333/): Memory corruption in DCMTK (high 8.4)
- [CVE-2024-27628](https://insights.sbomify.com/CVE-2024-27628/): Memory corruption in n/a (high 8.1)
- [CVE-2022-43272](https://insights.sbomify.com/CVE-2022-43272/): Denial of service in n/a (high 7.5)
- [CVE-2021-41687](https://insights.sbomify.com/CVE-2021-41687/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2357 and fix it if it is affected.

What it is: CVE-2025-2357 is a medium-severity memory corruption vulnerability in DCMTK, published on 17 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-2357 in the wild and no public exploit code.

Affected product: DCMTK. 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-2025-2357/ (Markdown: https://insights.sbomify.com/CVE-2025-2357/index.md)
```

## Sources

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

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