| Name | CVE-2019-16227 |
| Description | An issue was discovered in py-lmdb 0.97. For certain values of mn_flags, mdb_cursor_set triggers a memcpy with an invalid write operation within mdb_xcursor_init1. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| py-lmdb (PTS) | bullseye | 1.0.0-1 | vulnerable |
| bookworm | 1.4.0-1 | vulnerable |
| trixie, sid | 1.4.1-2 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| py-lmdb | source | (unstable) | (unfixed) | unimportant | | |
Notes
https://github.com/jnwatson/py-lmdb/issues/210
No real security issue in py-lmdb and disputed (MITRE contacted). If at all
then issues in underlying library but cf. https://github.com/jnwatson/py-lmdb/issues/210#issuecomment-531015023