Bug 1696145

Summary:	CVE-2019-1785 CVE-2019-1786 CVE-2019-1787 CVE-2019-1788 CVE-2019-1789 CVE-2019-1798 clamav: various flaws [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Dhananjay Arunesh <darunesh>
Component:	clamav	Assignee:	Sergio Basto <sergio>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	29	CC:	anon.amish, bennie.joubert, gbcox, janfrode, j, ondrejj, orion, redhat-bugzilla, rh-bugzilla, sergio, steve
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:	2019-06-30 02:40:16 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:	1696106, 1696110, 1696116, 1696134, 1696137, 1696143

Description Dhananjay Arunesh 2019-04-04 08:38:46 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-04-04 08:38:48 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=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1696106,1696110,1696116,1696134,1696137,1696143,1696145

# 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 Sergio Basto 2019-04-04 16:33:48 UTC

[1] Are the fixes , may I close all these bugs ? (except EPEL 6) only EPEL 6 aren't updated 

Thanks.

[1] 
https://bodhi.fedoraproject.org/updates/FEDORA-2019-06bbb43c20
https://bodhi.fedoraproject.org/updates/FEDORA-2019-fa59f1ed49
https://bodhi.fedoraproject.org/updates/FEDORA-2019-2903a24dce
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-75efbdf54f

Comment 3 Robert Scheck 2019-04-04 22:38:49 UTC

EPEL 6: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9c8cf7e4be

Comment 4 Sergio Basto 2019-04-04 23:37:17 UTC

I really fail to understand why we have 7 or more bug reports for one update. 

Robert I read some where that is not applicable to el6 , sorry my mistake .
I'm in clamav Mailing List , where they announce a security updated for 2 versions, I updated clamav in first day of the release but didn't read the blog , neither check el6 clamav version ... 

Thanks .