# CVE-2023-34474: Memory corruption in ImageMagick

> A local attacker can cause a denial of service by tricking a user into opening a specially crafted file in ImageMagick.

- **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:** 16 Jun 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-prvr-4vr9-qmvh, JLSEC-2026-909, SUSE-SU-2023:2878-1

## What is CVE-2023-34474?

CVE-2023-34474 is a medium-severity memory corruption vulnerability in Fedoraproject Extra Packages for Enterprise Linux, published on 16 Jun 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 heap-based buffer overflow issue was discovered in ImageMagick's ReadTIM2ImageData() function in coders/tim2.c. A local attacker could trick the user in opening specially crafted file, triggering an out-of-bounds read error, allowing an application to crash, resulting in a denial of service.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ImageMagick` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP4 | All versions | 7.1.0.9-150400.6.24.1 |
| `ImageMagick` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 7.1.0.9-150400.6.24.1 |
| `ImageMagick` | SUSE:Linux Enterprise Module for Development Tools 15 SP4 | All versions | 7.1.0.9-150400.6.24.1 |
| `ImageMagick` | SUSE:Linux Enterprise Module for Development Tools 15 SP5 | All versions | 7.1.0.9-150400.6.24.1 |
| `ImageMagick` | openSUSE:Leap 15.4 | All versions | 7.1.0.9-150400.6.24.1 |
| `ImageMagick` | openSUSE:Leap 15.5 | All versions | 7.1.0.9-150400.6.24.1 |

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

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

Apply the vendor's patch.

## Is CVE-2023-34474 being exploited?

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

## Other vulnerabilities in Fedoraproject Extra Packages for Enterprise Linux

- [CVE-2023-34152](https://insights.sbomify.com/CVE-2023-34152/): Command injection in ImageMagick (critical 9.8)
- [CVE-2022-4170](https://insights.sbomify.com/CVE-2022-4170/): Code injection in rxvt-unicode (critical 9.8)
- [CVE-2022-40315](https://insights.sbomify.com/CVE-2022-40315/): Moodle Minor SQL injection risk in admin user browsing (critical 9.8)
- [CVE-2022-45152](https://insights.sbomify.com/CVE-2022-45152/): Moodle blind Server-Side Request Forgery (SSRF) vulnerability in LTI provider library (critical 9.1)
- [CVE-2022-24882](https://insights.sbomify.com/CVE-2022-24882/): Server side NTLM does not properly check parameters in FreeRDP (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34474 is a medium-severity memory corruption vulnerability in Fedoraproject Extra Packages for Enterprise Linux, published on 16 Jun 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-34474 in the wild and no public exploit code.

Affected product: Fedoraproject Extra Packages for Enterprise 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-34474/ (Markdown: https://insights.sbomify.com/CVE-2023-34474/index.md)
```

## Sources

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

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