CVE-2019-16227
CRITICALCVSS 9.8/10EPSS 1.96%
Last modified
CVE-2019-16227 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 1.96% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Py-Lmdb Project | Py-Lmdb | <= 0.97 |
References
- https://github.com/TeamSeri0us/pocs/tree/master/lmdb/lmdb%20memcpy%20illegal%20dstExploit, Third Party Advisory
- https://github.com/TeamSeri0us/pocs/tree/master/lmdb/lmdb%20memcpy%20illegal%20dstExploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-16227?
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.
How severe is CVE-2019-16227?
CVE-2019-16227 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 1.96% probability of exploitation in the next 30 days.
How do I fix CVE-2019-16227?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2019-16227?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST