# CVE-2023-34151: Integer overflow in ImageMagick

> An integer overflow in ImageMagick's SVG and MVG coders can lead to undefined behavior, potentially causing crashes or arbitrary code execution.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** Yes
- **Published:** 30 May 2023
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2023-34151, GHSA-cm6m-2vvh-cxc6, JLSEC-2026-905, OESA-2023-1347, OESA-2023-1348, SUSE-SU-2023:2345-1, SUSE-SU-2023:2357-1, UBUNTU-CVE-2023-34151, USN-7440-1

## What is CVE-2023-34151?

CVE-2023-34151 is a medium-severity vulnerability in Debian Debian Linux, published on 30 May 2023. 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

A vulnerability was found in ImageMagick. This security flaw ouccers as an undefined behaviors of casting double to size_t in svg, mvg and other coders (recurring bugs of CVE-2022-32546).

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-34151?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ImageMagick` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 7.0.7.34-150200.10.48.1 |
| `ImageMagick` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 6.8.8.1-71.189.1 |
| `ImageMagick` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 6.8.8.1-71.189.1 |
| `ImageMagick` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 6.8.8.1-71.189.1 |
| `ImageMagick` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 6.8.8.1-71.189.1 |
| `ImageMagick` | openSUSE:Leap 15.4 | All versions | 7.0.7.34-150200.10.48.1 |

Products: Debian Debian Linux, Fedoraproject Extra Packages for Enterprise Linux, Fedoraproject Fedora, Imagemagick Imagemagick, Redhat Enterprise Linux.

## How do I fix CVE-2023-34151?

Apply the vendor's patch.

## Is CVE-2023-34151 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34151 and fix it if it is affected.

What it is: CVE-2023-34151 is a medium-severity vulnerability in Debian Debian Linux, published on 30 May 2023. 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-2023-34151 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2023-34151/ (Markdown: https://insights.sbomify.com/CVE-2023-34151/index.md)
```

## Sources

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

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