{"affected":[{"ecosystem_specific":{"binaries":[{"GraphicsMagick":"1.2.5-4.78.33.1","libGraphicsMagick2":"1.2.5-4.78.33.1","perl-GraphicsMagick":"1.2.5-4.78.33.1"}]},"package":{"ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","name":"GraphicsMagick","purl":"pkg:rpm/suse/GraphicsMagick&distro=SUSE%20Linux%20Enterprise%20Software%20Development%20Kit%2011%20SP4"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"1.2.5-4.78.33.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"GraphicsMagick":"1.2.5-4.78.33.1","libGraphicsMagick2":"1.2.5-4.78.33.1"}]},"package":{"ecosystem":"SUSE:Studio Onsite 1.3","name":"GraphicsMagick","purl":"pkg:rpm/suse/GraphicsMagick&distro=SUSE%20Studio%20Onsite%201.3"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"1.2.5-4.78.33.1"}],"type":"ECOSYSTEM"}]}],"aliases":[],"details":"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","id":"SUSE-SU-2018:0413-1","modified":"2018-02-09T14:54:21Z","published":"2018-02-09T14:54:21Z","references":[{"type":"ADVISORY","url":"https://www.suse.com/support/update/announcement/2018/suse-su-20180413-1/"},{"type":"REPORT","url":"https://bugzilla.suse.com/1043353"},{"type":"REPORT","url":"https://bugzilla.suse.com/1043354"},{"type":"REPORT","url":"https://bugzilla.suse.com/1047908"},{"type":"REPORT","url":"https://bugzilla.suse.com/1047910"},{"type":"REPORT","url":"https://bugzilla.suse.com/1050037"},{"type":"REPORT","url":"https://bugzilla.suse.com/1050072"},{"type":"REPORT","url":"https://bugzilla.suse.com/1050100"},{"type":"REPORT","url":"https://bugzilla.suse.com/1051442"},{"type":"REPORT","url":"https://bugzilla.suse.com/1052470"},{"type":"REPORT","url":"https://bugzilla.suse.com/1052708"},{"type":"REPORT","url":"https://bugzilla.suse.com/1052717"},{"type":"REPORT","url":"https://bugzilla.suse.com/1052768"},{"type":"REPORT","url":"https://bugzilla.suse.com/1052777"},{"type":"REPORT","url":"https://bugzilla.suse.com/1052781"},{"type":"REPORT","url":"https://bugzilla.suse.com/1054600"},{"type":"REPORT","url":"https://bugzilla.suse.com/1055038"},{"type":"REPORT","url":"https://bugzilla.suse.com/1055374"},{"type":"REPORT","url":"https://bugzilla.suse.com/1055455"},{"type":"REPORT","url":"https://bugzilla.suse.com/1055456"},{"type":"REPORT","url":"https://bugzilla.suse.com/1057000"},{"type":"REPORT","url":"https://bugzilla.suse.com/1060162"},{"type":"REPORT","url":"https://bugzilla.suse.com/1062752"},{"type":"REPORT","url":"https://bugzilla.suse.com/1067198"},{"type":"REPORT","url":"https://bugzilla.suse.com/1073690"},{"type":"REPORT","url":"https://bugzilla.suse.com/1074023"},{"type":"REPORT","url":"https://bugzilla.suse.com/1074120"},{"type":"REPORT","url":"https://bugzilla.suse.com/1074125"},{"type":"REPORT","url":"https://bugzilla.suse.com/1074175"},{"type":"REPORT","url":"https://bugzilla.suse.com/1075939"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2014-9811"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-10995"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-11102"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-11505"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-11526"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-11539"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-11750"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-12565"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-12640"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-12641"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-12643"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-12673"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-12676"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-12935"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-13065"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-13141"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-13142"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-13147"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-14103"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-14174"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-14649"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-15218"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-15238"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-16669"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-17501"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-17504"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-17782"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-17879"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-17884"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-17915"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-8352"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-9261"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2017-9262"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2018-5685"}],"related":["CVE-2014-9811","CVE-2017-10995","CVE-2017-11102","CVE-2017-11505","CVE-2017-11526","CVE-2017-11539","CVE-2017-11750","CVE-2017-12565","CVE-2017-12640","CVE-2017-12641","CVE-2017-12643","CVE-2017-12673","CVE-2017-12676","CVE-2017-12935","CVE-2017-13065","CVE-2017-13141","CVE-2017-13142","CVE-2017-13147","CVE-2017-14103","CVE-2017-14174","CVE-2017-14649","CVE-2017-15218","CVE-2017-15238","CVE-2017-16669","CVE-2017-17501","CVE-2017-17504","CVE-2017-17782","CVE-2017-17879","CVE-2017-17884","CVE-2017-17915","CVE-2017-8352","CVE-2017-9261","CVE-2017-9262","CVE-2018-5685"],"summary":"Security update for GraphicsMagick","upstream":["CVE-2014-9811","CVE-2017-10995","CVE-2017-11102","CVE-2017-11505","CVE-2017-11526","CVE-2017-11539","CVE-2017-11750","CVE-2017-12565","CVE-2017-12640","CVE-2017-12641","CVE-2017-12643","CVE-2017-12673","CVE-2017-12676","CVE-2017-12935","CVE-2017-13065","CVE-2017-13141","CVE-2017-13142","CVE-2017-13147","CVE-2017-14103","CVE-2017-14174","CVE-2017-14649","CVE-2017-15218","CVE-2017-15238","CVE-2017-16669","CVE-2017-17501","CVE-2017-17504","CVE-2017-17782","CVE-2017-17879","CVE-2017-17884","CVE-2017-17915","CVE-2017-8352","CVE-2017-9261","CVE-2017-9262","CVE-2018-5685"]}