Alerts This Week
Warning Icon 1 727
Alerts This Week
Warning Icon 1 727

Gentoo: GLSA-202101-20 Normal: libmaxminddb Security Flaw Detected

gentoo
Calendar Grey November 14, 2020
Dist Gentoo Esm H88
Gentoo Linux Advisory GLSA 202112-34 highlights a security vulnerability in libexampledb; patching advised.
A vulnerability in libmaxminddb could lead to a Denial of Service condition.

Summary

libmaxminddb used uninitialised memory when reading from a corrupt database file.

Resolution

All libmaxminddb users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libmaxminddb-1.4.3"

References

[ 1 ] CVE-2020-28241 https://nvd.nist.gov/vuln/detail/CVE-2020-28241

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202011-15
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: libmaxminddb: Denial of service
Date: November 14, 2020
Bugs: #753275
ID: 202011-15

Synopsis

A vulnerability in libmaxminddb could lead to a Denial of Service condition.

Background

The libmaxminddb library provides a C library for reading MaxMind DB files, including the GeoIP2 databases from MaxMind.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-libs/libmaxminddb < 1.4.3 >= 1.4.3

Impact

===== A remote attacker could entice a user to use a specially crafted database with libmaxminddb, possibly resulting in a Denial of Service condition.

Workaround

There is no known workaround at this time.

Your message here