CVE-2019-16225 py-lmdb Invalid write operation

Critical 9.8 Published 11 Sep 2019 Updated 5 Aug 2024

An attacker can trigger an invalid write in py-lmdb by supplying a malicious data file, potentially leading to code execution or denial of service.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2019-16225?

CVE-2019-16225 is a critical memory corruption vulnerability in n/a, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

An issue was discovered in py-lmdb 0.97. For certain values of mp_flags, mdb_page_touch does not properly set up mc->mc_pg[mc->top], leading to an invalid write operation. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker.

Weakness: CWE-787

Which versions are affected by CVE-2019-16225?

3 open source packages ship an affected version, including lmdb. It affects 1 product.

Package	Affected	Fixed in
`lmdb` PyPI	All versions to `0.97`	None
`lmdb` PyPI	All versions to `0.97`	None
`lmdb` PyPI	All versions	`0.98`

Products include Py-Lmdb Project Py-Lmdb.

How do I fix CVE-2019-16225?

Upgrade lmdb to 0.98 or later.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2019-16225 being exploited?

There is no known exploitation of CVE-2019-16225 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2019-16225, ECHO-b2ec-de08-80f1, GHSA-c74c-p4p7-r8q5, PYSEC-2019-237, UBUNTU-CVE-2019-16225.