Bug 1902005

Summary:	CVE-2020-0452 libexif: out of bounds write due to an integer overflow in exif-entry.c [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Marian Rehak <mrehak>
Component:	libexif	Assignee:	Yaakov Selkowitz <yselkowi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	33	CC:	ajax, caillon+fedoraproject, gnome-sig, mcatanza, rdieter, rhbugs, rhughes, rstrode, sandmann, thomasj, yselkowi
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-07 15:46:40 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:	1902004

Description Marian Rehak 2020-11-26 15:05:52 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 Marian Rehak 2020-11-26 15:05:55 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=high

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1902004,1902005

# 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 Michael Catanzaro 2020-12-03 14:16:51 UTC

This allows remote code interaction with no user interaction. Seems pretty urgent.

Comment 3 Marian Rehak 2020-12-07 09:16:59 UTC

You are correct, thank you for pointing it out. Honest mistake which shouldn't happen. Severity changed.

Comment 4 Michael Catanzaro 2020-12-07 15:08:50 UTC

Oops, I had meant to needinfo? Yaakov.

Comment 5 Yaakov Selkowitz 2020-12-07 15:18:32 UTC

You already have the patch in, what's the question for me?

Comment 6 Michael Catanzaro 2020-12-07 15:46:40 UTC

Well I had been checking to see if you'd noticed this bug, since it's been over a week and was high-severity.

But... wow, it seems I fixed this myself a month ago, before this bug was reported, and forgot that I had done so. This is especially interesting because I didn't realize I had commit access to this package. Apparently I discovered that I had commit access, fixed the issue, and then forgot all about having done so. So... yeah, this bug can be closed.