Bug 1895381

Summary:	CVE-2020-28241 libmaxminddb: improper initialization in dump_entry_data_list() in maxminddb.c [epel-all]
Product:	[Fedora] Fedora EPEL	Reporter:	Guilherme de Almeida Suckevicz <gsuckevi>
Component:	libmaxminddb	Assignee:	Igor Raits <igor.raits>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	epel7	CC:	igor.raits, jtfas90, jv+fedora, mruprich, ollie.yeoh
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:	2021-01-26 11:11:41 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:	1895379

Description Guilherme de Almeida Suckevicz 2020-11-06 14:31:12 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 epel-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 EPEL. 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 Guilherme de Almeida Suckevicz 2020-11-06 14:31:15 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=1895379,1895381

# 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 Michal Ruprich 2020-12-10 17:04:23 UTC

Hi Guilherme,

libmaxminddb is available in RHEL8 so it should not be available in epel. I fixed this bug in Fedora with the recent update but I am not sure why we have the tracking bug for epel.

Regards,
Michal

Comment 3 Guilherme de Almeida Suckevicz 2020-12-10 17:48:20 UTC

Hi Michal,

According to our manifests libmaxminddb is shipped in EPEL7 and that's the version which this bug was opened for.
Is that correct?

Thanks.

Comment 4 Michal Ruprich 2021-01-26 11:11:41 UTC

I don't see this as a critical problem that we need to solve. mmdblookup is a utility tool, not the library itself so I am closing this. Feel free to reopen should you feel that this should definitely be addressed.