{"answers":{"affected":"3 open source packages ship an affected version, including lmdb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16227 in the wild and no public exploit code.","fix":"Upgrade lmdb to 0.98 or later.","what":"CVE-2019-16227 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."},"fix_prompt":"Check this codebase for CVE-2019-16227 and fix it if it is affected.\n\nWhat it is: CVE-2019-16227 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.\nExploitation: There is no known exploitation of CVE-2019-16227 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- lmdb (PyPI): affected all versions up to 0.97; no fix listed\n- lmdb (PyPI): affected all versions up to 0.97; no fix listed\n- lmdb (PyPI): affected all versions; fixed in 0.98\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-16227/ (Markdown: https://insights.sbomify.com/CVE-2019-16227/index.md)","id":"CVE-2019-16227","markdown":"https://insights.sbomify.com/CVE-2019-16227/index.md","name":"CVE-2019-16227","record":{"aliases":["DEBIAN-CVE-2019-16227","ECHO-e174-ee41-e2ae","GHSA-pf3p-v9xp-mrvf","PYSEC-2019-239","UBUNTU-CVE-2019-16227"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python LMDB library","requires_auth":"none","summary":"An attacker can trigger memory corruption in the py-lmdb library by providing a malicious database file, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"py-lmdb","vendor":"py-lmdb_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"py-lmdb Invalid write operation","id":"CVE-2019-16227","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":3,"n_references":1,"next":{"headline":"py-lmdb Divide by Zero interruptions","id":"CVE-2019-16228"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.97"],"package":"lmdb","purl":null,"source":"GHSA-pf3p-v9xp-mrvf"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.97"],"package":"lmdb","purl":"pkg:pypi/lmdb","source":"GHSA-pf3p-v9xp-mrvf"},{"ecosystem":"PyPI","fixed":["0.98"],"introduced":["0"],"last_affected":[],"package":"lmdb","purl":"pkg:pypi/lmdb","source":"PYSEC-2019-239"}],"prev":{"headline":"LMDB invalid write","id":"CVE-2019-16226"},"products":["n/a"],"published":"2019-09-11","related":[{"cvss_score":9.8,"headline":"py-lmdb Invalid write operation","id":"CVE-2019-16224","kev_date_added":null,"published":"2019-09-11"},{"cvss_score":9.8,"headline":"py-lmdb Invalid write operation","id":"CVE-2019-16225","kev_date_added":null,"published":"2019-09-11"},{"cvss_score":7.5,"headline":"LMDB invalid write","id":"CVE-2019-16226","kev_date_added":null,"published":"2019-09-11"},{"cvss_score":7.5,"headline":"py-lmdb Divide by Zero interruptions","id":"CVE-2019-16228","kev_date_added":null,"published":"2019-09-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can trigger memory corruption in the py-lmdb library by providing a malicious database file, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2019-16227/"}