What is the CVSS score of CVE-2020-28241?

CVE-2020-28241 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H. EPSS exploitation probability: 2.1%.

Is there a public PoC exploit available for CVE-2020-28241?

Yes, a public proof-of-concept exploit is available for CVE-2020-28241. Prioritise patching immediately. EPSS: 2.1%.

Is there a patch available for CVE-2020-28241?

Yes, a patch is available for CVE-2020-28241. Update the affected software to the latest version immediately.

Libmaxminddb CVE-2020-28241

MEDIUM

Out-of-bounds Read (CWE-125)

2020-11-06 cve@mitre.org

Buffer Overflow Information Disclosure Libmaxminddb Debian Linux Fedora

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Nov 06, 2020 - 05:15 nvd

MEDIUM 6.5

DescriptionNVD

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

AnalysisAI

libmaxminddb before 1.4.3 has a heap-based buffer over-read in dump_entry_data_list in maxminddb.c. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Read (CWE-125), which allows attackers to read data from memory outside the intended buffer boundaries. libmaxminddb before 1.4.3 has a heap-based buffer over-read in dump_entry_data_list in maxminddb.c. Affected products include: Maxmind Libmaxminddb, Debian Debian Linux, Fedoraproject Fedora. Version information: before 1.4.3.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate array indices and buffer lengths. Use memory-safe languages. Enable AddressSanitizer during testing.