{"id":"CVE-2017-14174","aliases":["DEBIAN-CVE-2017-14174","DLA-1131-1","DLA-1785-1","DLA-2366-1","EUVD-2017-5684","GHSA-x8gv-j25j-89qm","SUSE-SU-2018:0017-1","SUSE-SU-2018:0043-1","SUSE-SU-2018:0197-1","SUSE-SU-2018:0413-1","UBUNTU-CVE-2017-14174","USN-3681-1"],"status":"published","title":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an...","description":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large \"length\" field in the header but does not contain sufficient backing data, is provided, the loop over \"length\" would consume huge CPU resources, since there is no EOF check inside the loop.","severity":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-08","score":0.02249,"percentile":0.83013,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-834"],"published":"2017-09-07T00:00:00Z","modified":"2026-10-24T14:12:10Z","fixes":[{"ecosystem":"Debian:12","package":"imagemagick","fixed_in":["8:6.9.9.34+dfsg-3"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"imagemagick","fixed_in":["8:6.9.9.34+dfsg-3"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"imagemagick","fixed_in":["8:6.9.9.34+dfsg-3"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"imagemagick","fixed_in":["8:6.7.7.10-6ubuntu3.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"imagemagick","fixed_in":["8:6.8.9.9-7ubuntu5.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"imagemagick","fixed_in":["8:6.9.7.4+dfsg-16ubuntu6.2"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.9.9.34+dfsg-3"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.9.9.34+dfsg-3"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.9.9.34+dfsg-3"}]}]},{"source":"osv","ecosystem":"Debian:7","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.7.7.10-5+deb7u17"}]}],"versions":["8:6.7.7.10-5","8:6.7.7.10-5+deb7u10","8:6.7.7.10-5+deb7u11","8:6.7.7.10-5+deb7u12","8:6.7.7.10-5+deb7u13","8:6.7.7.10-5+deb7u14","8:6.7.7.10-5+deb7u15","8:6.7.7.10-5+deb7u16","8:6.7.7.10-5+deb7u2","8:6.7.7.10-5+deb7u3","8:6.7.7.10-5+deb7u4","8:6.7.7.10-5+deb7u5","8:6.7.7.10-5+deb7u6","8:6.7.7.10-5+deb7u7","8:6.7.7.10-5+deb7u8","8:6.7.7.10-5+deb7u9"],"bundled":24},{"source":"osv","ecosystem":"Debian:8","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.8.9.9-5+deb8u16"}]}],"versions":["8:6.8.9.9-5","8:6.8.9.9-5+deb8u1","8:6.8.9.9-5+deb8u10","8:6.8.9.9-5+deb8u11","8:6.8.9.9-5+deb8u12","8:6.8.9.9-5+deb8u13","8:6.8.9.9-5+deb8u14","8:6.8.9.9-5+deb8u15","8:6.8.9.9-5+deb8u2","8:6.8.9.9-5+deb8u3","8:6.8.9.9-5+deb8u4","8:6.8.9.9-5+deb8u5","8:6.8.9.9-5+deb8u6","8:6.8.9.9-5+deb8u7","8:6.8.9.9-5+deb8u8","8:6.8.9.9-5+deb8u9"],"bundled":50},{"source":"osv","ecosystem":"Debian:9","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.9.7.4+dfsg-11+deb9u10"}]}],"versions":["8:6.9.7.4+dfsg-11","8:6.9.7.4+dfsg-11+deb9u1","8:6.9.7.4+dfsg-11+deb9u2","8:6.9.7.4+dfsg-11+deb9u3","8:6.9.7.4+dfsg-11+deb9u4","8:6.9.7.4+dfsg-11+deb9u5","8:6.9.7.4+dfsg-11+deb9u6","8:6.9.7.4+dfsg-11+deb9u7","8:6.9.7.4+dfsg-11+deb9u8","8:6.9.7.4+dfsg-11+deb9u9"],"bundled":50},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP2","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP3","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP2","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 12 SP2","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 12 SP3","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.8.1-71.20.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.3.6-7.78.17.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.3.6-7.78.17.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","package":"ImageMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.3.6-7.78.17.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","package":"GraphicsMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.5-4.78.28.2"}]}],"bundled":23},{"source":"osv","ecosystem":"SUSE:Studio Onsite 1.3","package":"GraphicsMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.5-4.78.28.2"}]}],"bundled":23},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","package":"GraphicsMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.5-4.78.33.1"}]}],"bundled":34},{"source":"osv","ecosystem":"SUSE:Studio Onsite 1.3","package":"GraphicsMagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.5-4.78.33.1"}]}],"bundled":34},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.7.7.10-6ubuntu3.11"}]}],"versions":["8:6.7.7.10-5ubuntu3","8:6.7.7.10-5ubuntu4","8:6.7.7.10-6ubuntu1","8:6.7.7.10-6ubuntu2","8:6.7.7.10-6ubuntu3","8:6.7.7.10-6ubuntu3.1","8:6.7.7.10-6ubuntu3.2","8:6.7.7.10-6ubuntu3.3","8:6.7.7.10-6ubuntu3.4","8:6.7.7.10-6ubuntu3.5","8:6.7.7.10-6ubuntu3.6","8:6.7.7.10-6ubuntu3.7","8:6.7.7.10-6ubuntu3.8","8:6.7.7.10-6ubuntu3.9"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.8.9.9-7ubuntu5.11"}]}],"versions":["8:6.8.9.9-5ubuntu2","8:6.8.9.9-6","8:6.8.9.9-6build1","8:6.8.9.9-7","8:6.8.9.9-7ubuntu1","8:6.8.9.9-7ubuntu2","8:6.8.9.9-7ubuntu3","8:6.8.9.9-7ubuntu4","8:6.8.9.9-7ubuntu5","8:6.8.9.9-7ubuntu5.1","8:6.8.9.9-7ubuntu5.2","8:6.8.9.9-7ubuntu5.3","8:6.8.9.9-7ubuntu5.4","8:6.8.9.9-7ubuntu5.5","8:6.8.9.9-7ubuntu5.6","8:6.8.9.9-7ubuntu5.7","8:6.8.9.9-7ubuntu5.8","8:6.8.9.9-7ubuntu5.9"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.9.7.4+dfsg-16ubuntu6.2"}]}],"versions":["8:6.9.7.4+dfsg-16ubuntu2","8:6.9.7.4+dfsg-16ubuntu3","8:6.9.7.4+dfsg-16ubuntu4","8:6.9.7.4+dfsg-16ubuntu5","8:6.9.7.4+dfsg-16ubuntu6"]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.7.7.10-6ubuntu3.11"}]}],"versions":["8:6.7.7.10-5ubuntu3","8:6.7.7.10-5ubuntu4","8:6.7.7.10-6ubuntu1","8:6.7.7.10-6ubuntu2","8:6.7.7.10-6ubuntu3","8:6.7.7.10-6ubuntu3.1","8:6.7.7.10-6ubuntu3.2","8:6.7.7.10-6ubuntu3.3","8:6.7.7.10-6ubuntu3.4","8:6.7.7.10-6ubuntu3.5","8:6.7.7.10-6ubuntu3.6","8:6.7.7.10-6ubuntu3.7","8:6.7.7.10-6ubuntu3.8","8:6.7.7.10-6ubuntu3.9"],"bundled":124},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.8.9.9-7ubuntu5.11"}]}],"versions":["8:6.8.9.9-5ubuntu2","8:6.8.9.9-6","8:6.8.9.9-6build1","8:6.8.9.9-7","8:6.8.9.9-7ubuntu1","8:6.8.9.9-7ubuntu2","8:6.8.9.9-7ubuntu3","8:6.8.9.9-7ubuntu4","8:6.8.9.9-7ubuntu5","8:6.8.9.9-7ubuntu5.1","8:6.8.9.9-7ubuntu5.2","8:6.8.9.9-7ubuntu5.3","8:6.8.9.9-7ubuntu5.4","8:6.8.9.9-7ubuntu5.5","8:6.8.9.9-7ubuntu5.6","8:6.8.9.9-7ubuntu5.7","8:6.8.9.9-7ubuntu5.8","8:6.8.9.9-7ubuntu5.9"],"bundled":124},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"imagemagick","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:6.9.7.4+dfsg-16ubuntu6.2"}]}],"versions":["8:6.9.7.4+dfsg-16ubuntu2","8:6.9.7.4+dfsg-16ubuntu3","8:6.9.7.4+dfsg-16ubuntu4","8:6.9.7.4+dfsg-16ubuntu5","8:6.9.7.4+dfsg-16ubuntu6"],"bundled":124}],"products":[{"vendor":"canonical","product":"ubuntu_linux"},{"vendor":"debian","product":"debian_linux"},{"vendor":"imagemagick","product":"imagemagick"}],"references":[{"url":"https://usn.ubuntu.com/3681-1/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"https://security.gentoo.org/glsa/201711-07","tags":["vendor-advisory","x_refsource_GENTOO","x_transferred","Third Party Advisory","advisory"]},{"url":"https://github.com/ImageMagick/ImageMagick/commit/f68a98a9d385838a1c73ec960a14102949940a64","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Third Party Advisory","report"]},{"url":"https://github.com/ImageMagick/ImageMagick/commit/04a567494786d5bb50894fc8bb8fea0cf496bea8","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix"]},{"url":"https://github.com/ImageMagick/ImageMagick/issues/714","tags":["x_refsource_CONFIRM","x_transferred","Exploit","Issue Tracking","Patch","Third Party Advisory","fix"]},{"url":"https://lists.debian.org/debian-lts-announce/2019/05/msg00015.html","tags":["mailing-list","x_refsource_MLIST","x_transferred","Third Party Advisory","advisory"]},{"url":"https://lists.debian.org/debian-lts-announce/2020/09/msg00007.html","tags":["mailing-list","x_refsource_MLIST","x_transferred","Third Party Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-14174"},{"url":"https://usn.ubuntu.com/3681-1"},{"url":"https://github.com/advisories/GHSA-x8gv-j25j-89qm"},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-14174","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20180017-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1052460","tags":["report"]},{"url":"https://bugzilla.suse.com/1055053","tags":["report"]},{"url":"https://bugzilla.suse.com/1055063","tags":["report"]},{"url":"https://bugzilla.suse.com/1056550","tags":["report"]},{"url":"https://bugzilla.suse.com/1057723","tags":["report"]},{"url":"https://bugzilla.suse.com/1058422","tags":["report"]},{"url":"https://bugzilla.suse.com/1063049","tags":["report"]},{"url":"https://bugzilla.suse.com/1063050","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15281","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20180043-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20180197-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1047044","tags":["report"]},{"url":"https://bugzilla.suse.com/1047054","tags":["report"]},{"url":"https://bugzilla.suse.com/1048457","tags":["report"]},{"url":"https://bugzilla.suse.com/1049373","tags":["report"]},{"url":"https://bugzilla.suse.com/1050129","tags":["report"]},{"url":"https://bugzilla.suse.com/1051412","tags":["report"]},{"url":"https://bugzilla.suse.com/1051847","tags":["report"]},{"url":"https://bugzilla.suse.com/1052252","tags":["report"]},{"url":"https://bugzilla.suse.com/1052758","tags":["report"]},{"url":"https://bugzilla.suse.com/1052764","tags":["report"]},{"url":"https://bugzilla.suse.com/1052771","tags":["report"]},{"url":"https://bugzilla.suse.com/1058082","tags":["report"]},{"url":"https://bugzilla.suse.com/1060577","tags":["report"]},{"url":"https://bugzilla.suse.com/1061587","tags":["report"]},{"url":"https://bugzilla.suse.com/1067177","tags":["report"]},{"url":"https://bugzilla.suse.com/1074969","tags":["report"]},{"url":"https://bugzilla.suse.com/1074975","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-10799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-10800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-18022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5247","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20180413-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1043353","tags":["report"]},{"url":"https://bugzilla.suse.com/1043354","tags":["report"]},{"url":"https://bugzilla.suse.com/1047908","tags":["report"]},{"url":"https://bugzilla.suse.com/1047910","tags":["report"]},{"url":"https://bugzilla.suse.com/1050037","tags":["report"]},{"url":"https://bugzilla.suse.com/1050072","tags":["report"]},{"url":"https://bugzilla.suse.com/1050100","tags":["report"]},{"url":"https://bugzilla.suse.com/1051442","tags":["report"]},{"url":"https://bugzilla.suse.com/1052470","tags":["report"]},{"url":"https://bugzilla.suse.com/1052708","tags":["report"]},{"url":"https://bugzilla.suse.com/1052717","tags":["report"]},{"url":"https://bugzilla.suse.com/1052768","tags":["report"]},{"url":"https://bugzilla.suse.com/1052777","tags":["report"]},{"url":"https://bugzilla.suse.com/1052781","tags":["report"]},{"url":"https://bugzilla.suse.com/1054600","tags":["report"]},{"url":"https://bugzilla.suse.com/1055038","tags":["report"]},{"url":"https://bugzilla.suse.com/1055374","tags":["report"]},{"url":"https://bugzilla.suse.com/1055455","tags":["report"]},{"url":"https://bugzilla.suse.com/1055456","tags":["report"]},{"url":"https://bugzilla.suse.com/1057000","tags":["report"]},{"url":"https://bugzilla.suse.com/1060162","tags":["report"]},{"url":"https://bugzilla.suse.com/1062752","tags":["report"]},{"url":"https://bugzilla.suse.com/1067198","tags":["report"]},{"url":"https://bugzilla.suse.com/1073690","tags":["report"]},{"url":"https://bugzilla.suse.com/1074023","tags":["report"]},{"url":"https://bugzilla.suse.com/1074120","tags":["report"]},{"url":"https://bugzilla.suse.com/1074125","tags":["report"]},{"url":"https://bugzilla.suse.com/1074175","tags":["report"]},{"url":"https://bugzilla.suse.com/1075939","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2014-9811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-10995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12641","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12643","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5685","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2017-14174","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3681-1","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-14174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-10995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-11640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12433","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12435","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-1000445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-1000476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-6405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-7443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-8804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-8960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-9133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-11251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-11625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-11655","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-11656","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2017-14174","description":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large \"length\" field in the header but does not contain sufficient backing data, is provided, the loop over \"length\" would consume huge CPU resources, since there is no EOF check inside the loop.","status":"published","published":"2017-09-07T06:00:00Z","modified":"2024-08-05T19:20:41.027Z","updated_at":"2026-11-02T14:33:11.928814Z"}],"euvd":[{"id":"EUVD-2017-5684","description":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large \"length\" field in the header but does not contain sufficient backing data, is provided, the loop over \"length\" would consume huge CPU resources, since there is no EOF check inside the loop.","status":"published","published":"2017-09-07T06:00:00Z","modified":"2024-08-05T19:20:41Z","updated_at":"2026-11-03T02:23:17.665061Z"}],"ghsa":[{"id":"GHSA-x8gv-j25j-89qm","title":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an...","description":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large \"length\" field in the header but does not contain sufficient backing data, is provided, the loop over \"length\" would consume huge CPU resources, since there is no EOF check inside the loop.","status":"published","published":"2022-05-13T01:14:07Z","modified":"2025-04-20T03:45:29Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-834"],"updated_at":"2026-11-02T15:01:51.665447Z"}],"nvd":[{"id":"CVE-2017-14174","description":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large \"length\" field in the header but does not contain sufficient backing data, is provided, the loop over \"length\" would consume huge CPU resources, since there is no EOF check inside the loop.","status":"published","published":"2017-09-07T06:29:00.39Z","modified":"2026-06-17T01:05:43.407Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"},{"version":"2.0","score":7.1,"vector":"AV:N/AC:M/Au:N/C:N/I:N/A:C","level":"high","assessor":"primary"}],"cwes":["CWE-834"],"updated_at":"2026-11-02T14:03:58.85945Z"}],"osv":[{"id":"CVE-2017-14174","description":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large \"length\" field in the header but does not contain sufficient backing data, is provided, the loop over \"length\" would consume huge CPU resources, since there is no EOF check inside the loop.","status":"published","published":"2017-09-07T06:29:00.39Z","modified":"2026-10-24T14:12:10.844862435Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:44:04.572713Z"},{"id":"DEBIAN-CVE-2017-14174","description":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large \"length\" field in the header but does not contain sufficient backing data, is provided, the loop over \"length\" would consume huge CPU resources, since there is no EOF check inside the loop.","status":"published","published":"2017-09-07T06:29:00.39Z","modified":"2026-09-01T20:03:43.694718144Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:28.801885Z"},{"id":"UBUNTU-CVE-2017-14174","description":"In coders/psd.c in ImageMagick 7.0.7-0 Q16, a DoS in ReadPSDLayersInternal() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted PSD file, which claims a large \"length\" field in the header but does not contain sufficient backing data, is provided, the loop over \"length\" would consume huge CPU resources, since there is no EOF check inside the loop.","status":"published","published":"2017-09-07T00:00:00Z","modified":"2026-04-22T11:15:30.751791Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"},{"version":"3.0","score":6.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:54:14.122973Z"},{"id":"DLA-1131-1","title":"imagemagick - security update","status":"published","published":"2017-10-10T00:00:00Z","modified":"2026-03-09T01:01:58.268586Z","updated_at":"2026-11-02T15:46:09.336894Z"},{"id":"DLA-1785-1","title":"imagemagick - security update","status":"published","published":"2019-05-13T00:00:00Z","modified":"2026-03-09T01:22:33.252689Z","updated_at":"2026-11-02T15:46:09.777694Z"},{"id":"DLA-2366-1","title":"imagemagick - security update","status":"published","published":"2020-09-07T00:00:00Z","modified":"2026-03-09T01:21:05.169049Z","updated_at":"2026-11-02T15:46:10.712745Z"},{"id":"SUSE-SU-2018:0017-1","title":"Security update for ImageMagick","description":"This update for ImageMagick fixes the following issues:\n\n- security update (xcf.c):\n  * CVE-2017-14343: Memory leak vulnerability in ReadXCFImage could lead to denial of service via a crafted file.\n    CVE-2017-12691: The ReadOneLayer function in coders/xcf.c allows remote attackers to cause a denial of service \n    (memory consumption) via a crafted file.\n    [bsc#1058422]\n\n- security update (pnm.c):\n  * CVE-2017-14042: A memory allocation failure was discovered in the ReadPNMImage function in coders/pnm.c and \n    could lead to remote denial of service [bsc#1056550]\n\n- security update (psd.c):\n  * CVE-2017-15281: ReadPSDImage allows remote attackers to cause a denial of service (application crash) or \n    possibly have unspecified other impact via a crafted file [bsc#1063049]\n  * CVE-2017-13061: A length-validation vulnerability was found in the function ReadPSDLayersInternal in coders/psd.c, \n    which allows attackers to cause a denial of service (ReadPSDImage memory exhaustion) via a crafted file. [bsc#1055063]\n  * CVE-2017-12563: A Memory exhaustion vulnerability was found in the function ReadPSDImage in coders/psd.c, \n    which allows attackers to cause a denial of service. [bsc#1052460]\n  * CVE-2017-14174: Due to a lack of an EOF check (End of File) in ReadPSDLayersInternal could cause huge CPU consumption, \n    when a crafted PSD file, which claims a large 'length' field in the header but does not contain sufficient backing data, \n    is provided, the loop over \\'length\\' would consume huge CPU resources, since there is no EOF check inside the loop.[bsc#1057723]\n\n- security update (meta.c):\n  * CVE-2017-13062: Amemory leak vulnerability was found in the function formatIPTC in coders/meta.c, \n    which allows attackers to cause a denial of service (WriteMETAImage memory consumption) via a crafted file [bsc#1055053]\n\n- security update (gif.c):\n  * CVE-2017-15277: ReadGIFImage in coders/gif.c leaves the palette uninitialized when processing a GIF file that has neither \n    a global nor local palette. If the affected product is used as a library loaded into a process that operates on interesting \n    data, this data sometimes can be leaked via the uninitialized palette.[bsc#1063050]\n","status":"published","published":"2018-01-04T08:59:18Z","modified":"2026-02-04T03:59:29.908486Z","updated_at":"2026-11-02T15:53:44.594517Z"},{"id":"SUSE-SU-2018:0043-1","title":"Security update for ImageMagick","description":"This update for ImageMagick fixes several issues.\n  \nThese security issues were fixed:\n\n- CVE-2017-14343: Fixed a memory leak vulnerability in ReadXCFImage in\n  coders/xcf.c via a crafted xcf image file (bsc#1058422).\n- CVE-2017-12691: The ReadOneLayer function in coders/xcf.c allowed remote\n  attackers to cause a denial of service (memory consumption) via a crafted file\n  (bsc#1058422).\n- CVE-2017-14042: Prevent memory allocation failure in the ReadPNMImage\n  function in coders/pnm.c. The vulnerability caused a big memory allocation,\n  which may have lead to remote denial of service in the MagickRealloc function\n  in magick/memory.c (bsc#1056550).\n- CVE-2017-15281: ReadPSDImage in coders/psd.c allowed remote attackers to\n  cause a denial of service (application crash) or possibly have unspecified\n  other impact via a crafted file (bsc#1063049).\n- CVE-2017-13061: A length-validation vulnerability in the function\n  ReadPSDLayersInternal in coders/psd.c allowed attackers to cause a denial of\n  service (ReadPSDImage memory exhaustion) via a crafted file (bsc#1055063).\n- CVE-2017-12563: A memory exhaustion vulnerability in the function\n  ReadPSDImage in coders/psd.c allowed attackers to cause a denial of service\n  (bsc#1052460).\n- CVE-2017-14174: coders/psd.c allowed for DoS in ReadPSDLayersInternal() due\n  to lack of an EOF (End of File) check might have caused huge CPU consumption.\n  When a crafted PSD file, which claims a large 'length' field in the header but\n  did not contain sufficient backing data, is provided, the loop over 'length'\n  would consume huge CPU resources, since there is no EOF check inside the loop\n  (bsc#1057723).\n- CVE-2017-13062: A memory leak vulnerability in the function formatIPTC in\n  coders/meta.c allowed attackers to cause a denial of service (WriteMETAImage\n  memory consumption) via a crafted file (bsc#1055053).\n- CVE-2017-15277: ReadGIFImage in coders/gif.c left the palette uninitialized\n  when processing a GIF file that has neither a global nor local palette. If this\n  functionality was used as a library loaded into a process that operates on\n  interesting data, this data sometimes could have been leaked via the\n  uninitialized palette (bsc#1063050).\n","status":"published","published":"2018-01-09T06:59:50Z","modified":"2026-02-04T02:34:22.003224Z","updated_at":"2026-11-02T15:53:44.594517Z"},{"id":"SUSE-SU-2018:0197-1","title":"Security update for GraphicsMagick","description":"This update for GraphicsMagick fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-14343: Fixed a memory leak vulnerability in ReadXCFImage in\n  coders/xcf.c via a crafted xcf image file (bsc#1058422)\n- CVE-2017-12691: The ReadOneLayer function in coders/xcf.c allowed remote\n  attackers to cause a denial of service (memory consumption) via a\n  crafted file (bsc#1058422)\n- CVE-2017-14042: Prevent memory allocation failure in the ReadPNMImage\n  function in coders/pnm.c. The vulnerability caused a big memory\n  allocation, which may have lead to remote denial of service in the\n  MagickRealloc function in magick/memory.c (bsc#1056550)\n- CVE-2017-13061: A length-validation vulnerability in the function\n  ReadPSDLayersInternal in coders/psd.c allowed attackers to cause a\n  denial of service (ReadPSDImage memory exhaustion) via a crafted file\n  (bsc#1055063)\n- CVE-2017-12563: A memory exhaustion vulnerability in the function\n  ReadPSDImage in coders/psd.c allowed attackers to cause a denial of service\n  (bsc#1052460)\n- CVE-2017-14174: coders/psd.c allowed for DoS in ReadPSDLayersInternal() due\n  to lack of an EOF (End of File) check might have caused huge CPU\n  consumption. When a crafted PSD file, which claims a large 'length'\n  field in the header but did not contain sufficient backing data, is\n  provided, the loop over 'length' would consume huge CPU resources,\n  since there is no EOF check inside the loop (bsc#1057723)\n- CVE-2017-15277: ReadGIFImage in coders/gif.c left the palette uninitialized\n  when processing a GIF file that has neither a global nor local palette. If this\n  functionality was used as a library loaded into a process that operates on\n  interesting data, this data sometimes could have been leaked via the\n  uninitialized palette (bsc#1063050)\n- CVE-2017-14733: ReadRLEImage in coders/rle.c mishandled RLE headers that\n  specified too few colors, which allowed remote attackers to cause a denial of\n  service (heap-based buffer over-read and application crash) via a crafted file\n  (bsc#1060577).\n- CVE-2017-12662: Fixed a memory leak vulnerability in WritePDFImage in\n  coders/pdf.c (bsc#1052758).\n- CVE-2017-14994: ReadDCMImage in coders/dcm.c allowed remote attackers to\n  cause a denial of service (NULL pointer dereference) via a crafted DICOM image,\n  related to the ability of DCM_ReadNonNativeImages to yield an image list\n  with zero frames (bsc#1061587).\n- CVE-2017-12140: The ReadDCMImage function in coders\\dcm.c had an integer\n  signedness error leading to excessive memory consumption via a crafted DCM file\n  (bsc#1051847).\n- CVE-2017-12644: Fixed memory leak vulnerability in ReadDCMImage in\n  coders\\dcm.c (bsc#1052764).\n- CVE-2017-11188: The ReadDPXImage function in coders\\dpx.c had a large loop\n  vulnerability that can cause CPU exhaustion via a crafted DPX file, related to\n  lack of an EOF check (bsc#1048457).\n- CVE-2017-10799: When processing a DPX image (with metadata indicating a large\n  width) in coders/dpx.c, a denial of service (OOM) could have occurred in\n  ReadDPXImage() (bsc#1047054).\n- CVE-2017-11449: coders/mpc did not enable seekable streams and thus could not\n  validate blob sizes, which allowed remote attackers to cause a denial of\n  service (application crash) or possibly have unspecified other impact via an\n  image received from stdin (bsc#1049373).\n- CVE-2017-11532: Prevent a memory leak vulnerability in the WriteMPCImage()\n  function in coders/mpc.c via a crafted file allowing for DoS (bsc#1050129).\n- CVE-2017-12430: A memory exhaustion in the function ReadMPCImage in\n  coders/mpc.c allowed attackers to cause DoS (bsc#1052252).\n- CVE-2017-12642: Prevent a memory leak vulnerability in ReadMPCImage in\n  coders\\mpc.c via crafted file allowing for DoS (bsc#1052771).\n- CVE-2017-14249: A mishandled EOF check in ReadMPCImage in coders/mpc.c that\n  lead to a division by zero in GetPixelCacheTileSize in MagickCore/cache.c\n  allowed remote attackers to cause a denial of service via a crafted file\n  (bsc#1058082).\n- CVE-2017-16547: The DrawImage function in magick/render.c did not properly\n  look for pop keywords that are associated with push keywords, which allowed\n  remote attackers to cause a denial of service (negative strncpy and application\n  crash) or possibly have unspecified other impact via a crafted file\n  (bsc#1067177).\n- Prevent memory leak via crafted file in pwp.c allowing for DoS (bsc#1051412)\n- CVE-2017-10800: Processing MATLAB images in coders/mat.c could have lead to a\n  denial of service (OOM) in ReadMATImage() if the size specified for a MAT\n  Object was larger than the actual amount of data (bsc#1047044).\n- CVE-2017-18022: Fixed memory leak vulnerability in MontageImageCommand in\n  MagickWand/montage.c (bsc#1074975).\n- CVE-2018-5247: Fixed memory leak vulnerability in ReadRLAImage in\n  coders/rla.c (bsc#1074969).\n","status":"published","published":"2018-01-24T14:43:19Z","modified":"2026-02-04T04:20:41.306335Z","updated_at":"2026-11-02T15:53:44.594517Z"},{"id":"SUSE-SU-2018:0413-1","title":"Security update for GraphicsMagick","description":"This update for GraphicsMagick fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-13065: Prevent NULL pointer dereference in the function SVGStartElement\n  (bsc#1055038).\n- CVE-2018-5685: Prevent infinite loop and application hang in the ReadBMPImage\n  function. Remote attackers could leverage this vulnerability to cause a denial\n  of service via an image file with a crafted bit-field mask value (bsc#1075939).\n- CVE-2017-9262: The ReadJNGImage function in coders/png.c allowed attackers to\n  cause a denial of service (memory leak) via a crafted file (bsc#1043353)\n- CVE-2017-9261: The ReadMNGImage function in coders/png.c allowed attackers to\n  cause a denial of service (memory leak) via a crafted file (bsc#1043354)\n- CVE-2017-10995: The mng_get_long function in coders/png.c allowed remote\n  attackers to cause a denial of service (heap-based buffer over-read and\n  application crash) via a crafted MNG image (bsc#1047908)\n- CVE-2017-11102: The ReadOneJNGImage function allowed remote attackers to\n  cause a denial of service (application crash) during JNG reading via a\n  zero-length color_image data structure (bsc#1047910).\n- CVE-2017-11539: Prevent memory leak in the ReadOnePNGImage() function in\n  coders/png.c (bsc#1050037)\n- CVE-2017-11505: The ReadOneJNGImage function in coders/png.c allowed remote\n  attackers to cause a denial of service (large loop and CPU consumption) via a\n  crafted file (bsc#1050072)\n- CVE-2017-11526: The ReadOneMNGImage function in coders/png.c allowed remote\n  attackers to cause a denial of service (large loop and CPU consumption) via a\n  crafted file (bsc#1050100)\n- CVE-2017-11750: The ReadOneJNGImage function in coders/png.c allowed remote\n  attackers to cause a denial of service (NULL pointer dereference) via a crafted\n  file (bsc#1051442)\n- CVE-2017-12565: Prevent memory leak in the function ReadOneJNGImage in\n  coders/png.c, which allowed attackers to cause a denial of service\n  (bsc#1052470)\n- CVE-2017-12676: Prevent memory leak in the function ReadOneJNGImage in\n  coders/png.c, which allowed attackers to cause a denial of service\n  (bsc#1052708)\n- CVE-2017-12673: Prevent memory leak in the function ReadOneMNGImage in\n  coders/png.c, which allowed attackers to cause a denial of service\n  (bsc#1052717)\n- CVE-2017-12643: Prevent a memory exhaustion vulnerability in ReadOneJNGImage\n  in coders\\png.c (bsc#1052768)\n- CVE-2017-12641: Prevent a memory leak vulnerability in ReadOneJNGImage in\n  coders\\png.c (bsc#1052777)\n- CVE-2017-12640: Prevent an out-of-bounds read vulnerability in\n  ReadOneMNGImage in coders/png.c (bsc#1052781)\n- CVE-2017-12935: The ReadMNGImage function in coders/png.c mishandled large\n  MNG images, leading to an invalid memory read in the SetImageColorCallBack\n  function in magick/image.c (bsc#1054600)\n- CVE-2017-13147: Prevent allocation failure in the function ReadMNGImage in\n  coders/png.c when a small MNG file has a MEND chunk with a large length value\n  (bsc#1055374)\n- CVE-2017-13142: Added additional checks for short files to prevent a crafted\n  PNG file from triggering a crash (bsc#1055455)\n- CVE-2017-13141: Prevent memory leak in ReadOnePNGImage in coders/png.c\n  (bsc#1055456)\n- CVE-2017-14103: The ReadJNGImage and ReadOneJNGImage functions in\n  coders/png.c did not properly manage image pointers after certain error\n  conditions, which allowed remote attackers to conduct use-after-free attacks\n  via a crafted file, related to a ReadMNGImage out-of-order CloseBlob call\n  (bsc#1057000)\n- CVE-2017-14649: ReadOneJNGImage in coders/png.c did not properly validate JNG\n  data, leading to a denial of service (assertion failure in\n  magick/pixel_cache.c, and application crash) (bsc#1060162)\n- CVE-2017-15218: Prevent memory leak in ReadOneJNGImage in coders/png.c\n  (bsc#1062752)\n- CVE-2017-15238: ReadOneJNGImage had a use-after-free issue when the height or\n  width is zero, related to ReadJNGImage (bsc#1067198).\n- CVE-2017-17782: Prevent heap-based buffer over-read in ReadOneJNGImage\n  related to oFFs chunk allocation (bsc#1073690).\n- CVE-2017-17501: WriteOnePNGImage had a heap-based buffer over-read that could\n  be triggered via a crafted file (bsc#1074023).\n- CVE-2017-17884: Prevent memory leak in the function WriteOnePNGImage in\n  coders/png.c, which allowed attackers to cause a denial of service via a\n  crafted PNG image file (bsc#1074120)\n- CVE-2017-17879: Prevent heap-based buffer over-read in ReadOneMNGImage in\n  coders/png.c, related to length calculation and caused by an off-by-one error\n  (bsc#1074125)\n- CVE-2017-17915: Prevent heap-based buffer over-read in ReadMNGImage when\n  accessing one byte testing whether a limit has been reached (bsc#1074175).\n","status":"published","published":"2018-02-09T14:54:21Z","modified":"2026-02-04T02:37:48.167723Z","updated_at":"2026-11-02T15:53:44.594517Z"},{"id":"USN-3681-1","title":"imagemagick vulnerabilities","description":"It was discovered that ImageMagick incorrectly handled certain malformed\nimage files. If a user or automated system using ImageMagick were tricked\ninto opening a specially crafted image, an attacker could exploit this to\ncause a denial of service or possibly execute code with the privileges of\nthe user invoking the program.\n","status":"published","published":"2018-06-12T11:40:14Z","modified":"2026-04-22T09:46:51.738947Z","updated_at":"2026-11-02T16:58:13.496563Z"}]}}