# CVE-2024-41817: Arbitrary Code Execution in `AppImage` version `ImageMagick`

> Attackers can execute arbitrary code by placing malicious files in the current working directory due to unsafe environment variable handling in the AppImage version.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-8rxc-922v-phg8, JLSEC-2026-913

## What is CVE-2024-41817?

CVE-2024-41817 is a high-severity code injection vulnerability in Imagemagick Imagemagick, published on 29 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ImageMagick is a free and open-source software suite, used for editing and manipulating digital images. The `AppImage` version `ImageMagick` might use an empty path when setting `MAGICK_CONFIGURE_PATH` and `LD_LIBRARY_PATH` environment variables while executing, which might lead to arbitrary code execution by loading malicious configuration files or shared libraries in the current working directory while executing `ImageMagick`. The vulnerability is fixed in 7.11-36.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Imagemagick Imagemagick.

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

Upgrade to a fixed version.

## Is CVE-2024-41817 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41817 exists.

Public exploit code:

- CVE-2024-41817 POC ImageMagick <= 7.1.1-35 Arbitrary Code Execution (github_poc): https://github.com/Dxsk/CVE-2024-41817-poc
- This is an automated exploitation script for the Hack The Box machine *Titanic*. It extracts Gitea user hashes via LFI, assists in cracking them, and exploits an ImageMagick vulnerability (CVE-2024-41817) to gain root access via a malicious shared library. (github_poc): https://github.com/maikneysm/AutoPwn-Titanic.htb

## Other vulnerabilities in Imagemagick Imagemagick

- [CVE-2019-19952](https://insights.sbomify.com/CVE-2019-19952/): Use after free in n/a (critical 9.8)
- [CVE-2018-16328](https://insights.sbomify.com/CVE-2018-16328/): Null dereference in n/a (critical 9.8)
- [CVE-2018-16329](https://insights.sbomify.com/CVE-2018-16329/): Null dereference in n/a (critical 9.8)
- [CVE-2017-18210](https://insights.sbomify.com/CVE-2017-18210/): Null dereference in n/a (critical 9.8)
- [CVE-2017-14138](https://insights.sbomify.com/CVE-2017-14138/): Denial of service in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41817 is a high-severity code injection vulnerability in Imagemagick Imagemagick, published on 29 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41817 exists.

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

## Sources

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

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