Bug 19445

Summary: mupdf new use-after-free security issue + security issues in mutool (and mujstest, but not affecting us)
Product: Mageia Reporter: David Walser <luigiwalser>
Component: SecurityAssignee: Rémi Verschelde <rverschelde>
Status: RESOLVED FIXED QA Contact: Sec team <security>
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: mupdf-1.8-6.mga6.src.rpm CVE:
Status comment:

Description David Walser 2016-09-23 03:05:45 CEST
A CVE has been requested for an upstream fix in mupdf:
http://openwall.com/lists/oss-security/2016/09/22/7

The commit to fix the issue is linked near the bottom of the message.  They mentioned it will be in 1.10, so maybe there was a 1.9 we missed.
Rémi Verschelde 2016-09-23 09:30:11 CEST

Status: NEW => ASSIGNED

Comment 2 Rémi Verschelde 2016-10-01 16:59:46 CEST
I'm updating mupdf to 1.9a, and adding the relevant patches.

As I've fully unbundled mujs and don't package mujstest, I'll only cherry-pick the commits for the infinite loop in mutool and the use after free in pdf_to_num.

Summary: mupdf new use-after-free security issue + security issues in mutool and mujstest => mupdf new use-after-free security issue + security issues in mutool (and mujstest, but not affecting us)

Comment 3 Rémi Verschelde 2016-10-02 17:08:07 CEST
I dropped the package from Cauldron for various reasons: having to unbundle mujs is messy, nothing relies on this package, the current git master HEAD generates 34 MB stripped binaries for a "lightweight" PDF reader... And there are good alternatives already packaged.

Until upstream does some work on their packaging-friendliness (mujs as shared library, libmupdf as shared library, instead of both as bundled ones), this does not bring much added value to the distro, just more security burden.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED