Bug 1582316

Summary:	CVE-2018-1000036 CVE-2018-1000037 CVE-2018-1000038 CVE-2018-1000039 CVE-2018-1000040 mupdf: various flaws [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Laura Pardo <lpardo>
Component:	mupdf	Assignee:	Michael J Gruber <mjg>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	28	CC:	mjg
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:	2018-06-10 12:13:50 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:
Bug Depends On:
Bug Blocks:	1582311, 1582312, 1582313, 1582314, 1582315

Description Laura Pardo 2018-05-24 20:46:47 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 Laura Pardo 2018-05-24 20:46:51 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

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1582315,1582316

# 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 Laura Pardo 2018-05-24 20:47:55 UTC

Added new parent flaw bug 1582311 (CVE-2018-1000040), 1582312 (CVE-2018-1000039), 1582313 (CVE-2018-1000038), 1582314 (CVE-2018-1000037) to this tracking bug.

Comment 3 Michael J Gruber 2018-06-10 11:33:25 UTC

What sense does it make to track all these different blockers here under a common bug against the mupdf component, whith individual blockers filed against the vulnerability component?

Am I supposed to reference (and close) vulnerability bugs in my mupdf updates? No!

I'm supposed to fix and close mupdf bugs, and I can't work with this bug here when some of the referenced bugs have fixes and some haven't.

The dependency chain is all wrong, and the automatic template (listing dependent and depending bug) is wrong.

Comment 4 Michael J Gruber 2018-06-10 12:13:50 UTC

All bugs that are listed under "blocks" (which should have been reported against mupdf, and listed under "depends on" for this one, which should have been reported against viln.) checked (and closed) individually, all fixed in 1.13.0.

So, closing this one manually.