# CVE-2024-27628: Memory corruption in n/a

> A buffer overflow in DCMTK allows attackers to execute arbitrary code via the EctEnhancedCT method, requiring an upgrade to mitigate.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-27628, GHSA-4vfx-5jf7-gfhv, MGASA-2024-0380, UBUNTU-CVE-2024-27628

## What is CVE-2024-27628?

CVE-2024-27628 is a high-severity memory corruption vulnerability in n/a, published on 28 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer Overflow vulnerability in DCMTK v.3.6.8 allows an attacker to execute arbitrary code via the EctEnhancedCT method component.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Offis Dcmtk.

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

Upgrade to a fixed version.

## Is CVE-2024-27628 being exploited?

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

## Other vulnerabilities in n/a

- [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-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)
- [CVE-2021-41688](https://insights.sbomify.com/CVE-2021-41688/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27628 is a high-severity memory corruption vulnerability in n/a, published on 28 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-27628 in the wild and no public exploit code.

Affected product: n/a. 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-27628/ (Markdown: https://insights.sbomify.com/CVE-2024-27628/index.md)
```

## Sources

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

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