Bug 1667323

Summary:	CVE-2019-6130 python-PyMuPDF: mupdf: NULL pointer deference in fz_load_page() in fitz/document.c [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Dhananjay Arunesh <darunesh>
Component:	python-PyMuPDF	Assignee:	Scott Talbert <swt>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	29	CC:	anemec, swt
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-18 09:31:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dhananjay Arunesh 2019-01-18 07:39:10 UTC

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Comment 1 Dhananjay Arunesh 2019-01-18 07:39:12 UTC

Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=low

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1667309,1667323

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Scott Talbert 2019-01-18 14:28:39 UTC

@Andrej Nemec, why did you close this as NOTABUG?

Comment 3 Andrej Nemec 2019-01-18 15:29:37 UTC

(In reply to Scott Talbert from comment #2)
> @Andrej Nemec, why did you close this as NOTABUG?

Hi Scott, we did not find any reference that this CVE affected python-PyMuPDF. It affects mupdf and relevant tracker was opened.

Comment 4 Scott Talbert 2019-01-18 16:02:46 UTC

(In reply to Andrej Nemec from comment #3)
> (In reply to Scott Talbert from comment #2)
> > @Andrej Nemec, why did you close this as NOTABUG?
> 
> Hi Scott, we did not find any reference that this CVE affected
> python-PyMuPDF. It affects mupdf and relevant tracker was opened.

Unfortunately, mupdf does not provide shared libraries, only static.  Thus, python-PyMuPDF is statically linked with mupdf and as a result, all CVEs that affect mupdf could apply to PyMuPDF too.  The good news is that once mupdf fixes these CVEs, python-PyMuPDF just needs a corresponding rebuild.  I haven't looked closely at the CVE details to see if this is something that couldn't be exploited via Python, though.