CVE-2019-16228

Exp

An issue was discovered in py-lmdb 0.97. There is a divide-by-zero error in the function mdb_env_open2 if mdb_env_read_header obtains a zero value for a certain size field. NOTE: this outcome occurs when accessing a data.mdb file supplied by an attacker.

Published: 2019-09-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-16228 is rated High Exploit Risk (61.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.25%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-16228

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-16228

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-21 0.29% 0.25% -0.04%
2 2026-01-29 0.17% 0.29% +0.12%
3 2025-11-21 — 0.17% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-16228

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-16228

GitHub Security Advisory for CVE-2019-16228

GHSA-ggwq-vrgp-6gv4 · Severity: high · Ecosystem: pip — py-lmdb Divide by Zero interruptions

OS Trackers for CVE-2019-16228

vendor priority summary link
debian not yet assigned CVE-2019-16228 not yet assigned priority: Debian including 1 source packages (py-lmdb), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2019-16228
ubuntu medium CVE-2019-16228 medium priority: Ubuntu including 1 source packages (py-lmdb), 18 status rows across 18 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 10, needs-triage 7, DNE 1. https://ubuntu.com/security/CVE-2019-16228

Affected software / configurations for CVE-2019-16228

Vendor Product Version Raw CPE
py-lmdb_project py-lmdb <= 0.97 cpe:2.3:a:py-lmdb_project:py-lmdb:*:*:*:*:*:*:*:*

References for CVE-2019-16228

URL Tags
https://github.com/TeamSeri0us/pocs/tree/master/lmdb/FPE Exploit Third Party Advisory
cvelogic Threat Intelligence