Bug 2082200

Summary:	CVE-2022-20796 clamav: NULL-pointer dereference crash in the scan verdict cache check [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Patrick Del Bello <pdelbell>
Component:	clamav	Assignee:	Sergio Basto <sergio>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	35	CC:	anon.amish, bennie.joubert, gbcox, janfrode, j, lee.jnk, ondrejj, orion, pgnet.dev, redhat-bugzilla, rh-bugzilla, sergio, steve
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	clamav-0.103.6-1.fc36 clamav-0.103.6-1.fc34 clamav-0.103.6-1.fc35	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-16 01:07:57 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:	2082198

Description Patrick Del Bello 2022-05-05 14:53:20 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 Patrick Del Bello 2022-05-05 14:53:23 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=2082198,2082200

# 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 Fedora Update System 2022-05-06 13:33:39 UTC

FEDORA-2022-b8691af27b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8691af27b

Comment 3 Fedora Update System 2022-05-06 13:34:01 UTC

FEDORA-2022-0ac71a8f3a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ac71a8f3a

Comment 4 Fedora Update System 2022-05-06 13:34:29 UTC

FEDORA-2022-a910a41a17 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a910a41a17

Comment 5 Fedora Update System 2022-05-08 03:06:27 UTC

FEDORA-2022-b8691af27b has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b8691af27b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b8691af27b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-05-08 03:27:04 UTC

FEDORA-2022-0ac71a8f3a has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0ac71a8f3a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ac71a8f3a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-05-08 04:06:22 UTC

FEDORA-2022-a910a41a17 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a910a41a17`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a910a41a17

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-05-16 01:07:57 UTC

FEDORA-2022-b8691af27b has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2022-05-16 01:43:54 UTC

FEDORA-2022-a910a41a17 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-05-16 02:04:48 UTC

FEDORA-2022-0ac71a8f3a has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.