CVE-2020-28241

libmaxminddb before 1.4.3 has a heap-based buffer over-read in dump_entry_data_list in maxminddb.c.

The product reads data past the end, or before the beginning, of the intended buffer.

Name	Vendor	Start Version	End Version
Libmaxminddb	Maxmind	*	1.4.3 (excluding)
Red Hat Enterprise Linux 8	RedHat	libmaxminddb-0:1.2.0-10.el8_9.1	*
Red Hat Enterprise Linux 8.6 Extended Update Support	RedHat	libmaxminddb-0:1.2.0-10.el8_6.1	*
Red Hat Enterprise Linux 8.8 Extended Update Support	RedHat	libmaxminddb-0:1.2.0-10.el8_8.1	*
RHEL-8 based Middleware Containers	RedHat	rh-sso-7/sso76-openshift-rhel8:7.6-42	*
RHEL-8 based Middleware Containers	RedHat	rh-sso-7/sso7-rhel8-operator-bundle:7.6.7-4	*
Libmaxminddb	Ubuntu	bionic	*
Libmaxminddb	Ubuntu	devel	*
Libmaxminddb	Ubuntu	esm-apps/bionic	*
Libmaxminddb	Ubuntu	esm-apps/xenial	*
Libmaxminddb	Ubuntu	focal	*
Libmaxminddb	Ubuntu	groovy	*
Libmaxminddb	Ubuntu	hirsute	*
Libmaxminddb	Ubuntu	impish	*
Libmaxminddb	Ubuntu	jammy	*
Libmaxminddb	Ubuntu	kinetic	*
Libmaxminddb	Ubuntu	lunar	*
Libmaxminddb	Ubuntu	mantic	*
Libmaxminddb	Ubuntu	noble	*
Libmaxminddb	Ubuntu	oracular	*
Libmaxminddb	Ubuntu	trusty	*
Libmaxminddb	Ubuntu	upstream	*
Libmaxminddb	Ubuntu	xenial	*

Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2020-28241
CWE	https://cwe.mitre.org/data/definitions/125.html

Out-of-bounds Read