Issue when Configuring the ImageMagick Security Policy
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ImageMagick | ImageMagick | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3429-1 | imagemagick security update |
EUVD |
EUVD-2021-25590 | ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. In affected versions and in certain cases, Postscript files could be read and written when specifically excluded by a `module` policy in `policy.xml`. ex. <policy domain="module" rights="none" pattern="PS" />. The issue has been resolved in ImageMagick 7.1.0-7 and in 6.9.12-22. Fortunately, in the wild, few users utilize the `module` policy and instead use the `coder` policy that is also our workaround recommendation: <policy domain="coder" rights="none" pattern="{PS,EPI,EPS,EPSF,EPSI}" />. |
Ubuntu USN |
USN-5736-1 | ImageMagick vulnerabilities |
Ubuntu USN |
USN-5736-2 | ImageMagick vulnerabilities |
Ubuntu USN |
USN-6200-1 | ImageMagick vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.353% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.