In MuPDF 1.12.0 and earlier, multiple use of uninitialized values in the PDF parser could allow an attacker to cause a denial of service (crash) or influence program flow via a crafted file. References: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5596 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5600 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5603 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5609 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5610 Patch: http://git.ghostscript.com/?p=mupdf.git;a=commitdiff;h=83d4dae44c71816c084a635550acc1a51529b881;hp=f597300439e62f5e921f0d7b1e880b5c1a1f1607
Created mupdf tracking bugs for this issue: Affects: fedora-all [bug 1582316]
Fixed in 1.13.0 Closing here since 1582316 is bogus (tracker should be here and depend on various blockers against mupdf, not the other way round).