CVE-2017-11446: Medium severity ImageMagick ImageMagick vulnerability
Published Jul 19, 2017
·Updated
The ReadPESImage function in coders\pes.c in ImageMagick 7.0.6-1 has a ...
Affected Software
2 affected componentsFixes available
ImageMagick ImageMagick=7.0.6-1
debian/imagemagick
8:6.9.11.60+dfsg-1.6+deb12u118:6.9.11.60+dfsg-1.6+deb12u158:7.1.1.43+dfsg1-1+deb13u128:7.1.1.43+dfsg1-1+deb13u138:7.1.2.34+dfsg1-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/imagemagickto a version that resolves this vulnerability.Fixed in 8:6.9.11.60+dfsg-1.6+deb12u11Fixed in 8:6.9.11.60+dfsg-1.6+deb12u15Fixed in 8:7.1.1.43+dfsg1-1+deb13u12Fixed in 8:7.1.1.43+dfsg1-1+deb13u13Fixed in 8:7.1.2.34+dfsg1-1
Event History
Jul 19, 2017
CVE Published
via MITRE·07:00 AM
Data Sourced
via MITRE·07:00 AM
Description
Event
07:29 AM
Frequently Asked Questions
1
What is the severity of CVE-2017-11446?
CVE-2017-11446 is considered a high severity vulnerability due to its potential to cause CPU exhaustion.
2
How do I fix CVE-2017-11446?
To fix CVE-2017-11446, update ImageMagick to a version that is not vulnerable, specifically versions above 7.0.6-1.
3
What versions of ImageMagick are affected by CVE-2017-11446?
ImageMagick versions 7.0.6-1 are affected by CVE-2017-11446.
4
What kind of vulnerability is CVE-2017-11446?
CVE-2017-11446 is an infinite loop vulnerability that can be exploited through crafted PES files.
5
Can I use ImageMagick safely after addressing CVE-2017-11446?
Yes, after upgrading to a safe version, ImageMagick can be used without the risk associated with CVE-2017-11446.