CVE-2019-16225

Publication date 11 September 2019

Last updated 12 January 2026


Ubuntu priority

Cvss 3 Severity Score

9.8 · Critical

Score breakdown

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.

Read the notes from the security team

Status

Package Ubuntu Release Status
py-lmdb 25.10 questing
Needs evaluation
25.04 plucky Ignored end of life, was needs-triage
24.10 oracular Ignored end of life, was needs-triage
24.04 LTS noble
Needs evaluation
23.10 mantic Ignored end of life, was needs-triage
23.04 lunar Ignored end of life, was needs-triage
22.10 kinetic Ignored end of life, was needs-triage
22.04 LTS jammy
Needs evaluation
21.10 impish Ignored end of life
21.04 hirsute Ignored end of life
20.10 groovy Ignored end of life
20.04 LTS focal
Needs evaluation
19.10 eoan Ignored end of life
19.04 disco Ignored end of life
18.04 LTS bionic
Needs evaluation
16.04 LTS xenial
Needs evaluation
14.04 LTS trusty Not in release

Notes


vyomydv

CVE disputed - no security issue in py-lmdb. MITRE has been contacted. This CVE is incorrectly attributed to py-lmdb, which is a Python binding for the LMDB C library, not an independent implementation. The reported issue involves loading a corrupted LMDB database, which would be a matter for the underlying liblmdb C library, not the Python bindings. Additionally, the liblmdb project has historically not accepted corrupted databases created through fuzzing as security vulnerabilities, absent real-world corruption scenarios (e.g., OS crashes, hardware failures).

Severity score breakdown

Parameter Value
Base score 9.8 · Critical
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Scope Unchanged
Confidentiality High
Integrity impact High
Availability impact High
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H