Hide Forgot
libjpeg-turbo through version 1.5.90 is vulnerable to a divide by zero flaw in the rdbmp.c:start_input_bmp() function. An attacker could exploit this to cause a denial of service via crafted BMP image. External Reference: https://www.tenable.com/security/research/tra-2018-17 Upstream patch: https://github.com/libjpeg-turbo/libjpeg-turbo/commit/43e84cff1bb2bd8293066f6ac4eb0df61ddddbc6
Created libjpeg-turbo tracking bugs for this issue: Affects: fedora-all [bug 1593555] Created mingw-libjpeg-turbo tracking bugs for this issue: Affects: epel-all [bug 1593556]
Created mingw-libjpeg-turbo tracking bugs for this issue: Affects: epel-7 [bug 1593558]
The floating point exception actually happens in the "alloc_sarray()" function, although the patch adds checks to "start_input_bmp()" function. The cjpeg binaries we ship in RHEL7 refuse to load the specially crafted BMP file. It seems like the only obvious vector is via the "tjLoadImage()" function, which was added to 2.x versions and is not yet available in versions we ship in RHEL6/7.
Statement: This issue did not affect the versions of libjpeg-turbo as shipped with Red Hat Enterprise Linux 6 and 7.