# SUSE-SU-2018:2562-1: Security update for ImageMagick

> Attackers can execute arbitrary code via malicious PostScript or PDF files processed by ImageMagick, requiring user interaction to open the file.

- **Severity:** Not scored
- **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:** 30 Aug 2018

## What is SUSE-SU-2018:2562-1?

SUSE-SU-2018:2562-1 is a code injection vulnerability in ImageMagick, published on 30 Aug 2018. 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

This update for ImageMagick fixes the following issues:

Security issue fixed:

- Disable PS, PS2, PS3, XPS and PDF coders in default policy.xml (bsc#1105592)

## Which versions are affected by SUSE-SU-2018:2562-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ImageMagick` | SUSE:Linux Enterprise Module for Desktop Applications 15 | All versions | 7.0.7.34-3.17.1 |
| `ImageMagick` | SUSE:Linux Enterprise Module for Development Tools 15 | All versions | 7.0.7.34-3.17.1 |

## How do I fix SUSE-SU-2018:2562-1?

Apply the vendor's patch.

## Is SUSE-SU-2018:2562-1 being exploited?

There is no known exploitation of SUSE-SU-2018:2562-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2018:2562-1 and fix it if it is affected.

What it is: SUSE-SU-2018:2562-1 is a code injection vulnerability in ImageMagick, published on 30 Aug 2018. 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 SUSE-SU-2018:2562-1 in the wild and no public exploit code.

Affected product: 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/SUSE-SU-2018-2562-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-2562-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2018:2562-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2018-2562-1/
Summaries are generated and may contain mistakes; the official description above is the record.