{"answers":{"affected":"3 open source packages ship an affected version, including generator. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16144 in the wild and no public exploit code.","fix":"Upgrade generator to 0.6.18 or later.","what":"CVE-2019-16144 is a high-severity memory corruption vulnerability in n/a, published on 9 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-16144 and fix it if it is affected.\n\nWhat it is: CVE-2019-16144 is a high-severity memory corruption vulnerability in n/a, published on 9 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-16144 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- generator (crates.io): affected all versions; fixed in 0.6.18\n- generator (crates.io): affected all versions; fixed in 0.6.18\n- generator (crates.io): affected from 0.0.0-0; fixed in 0.6.18\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-16144/ (Markdown: https://insights.sbomify.com/CVE-2019-16144/index.md)","id":"CVE-2019-16144","markdown":"https://insights.sbomify.com/CVE-2019-16144/index.md","name":"CVE-2019-16144","record":{"aliases":["GHSA-6c65-xcf5-299x","RUSTSEC-2019-0020"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust generator crate","requires_auth":"none","summary":"Attackers can exploit uninitialized memory in the Rust generator crate to potentially disclose sensitive data or execute arbitrary code.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"generator-rs","vendor":"generator-rs_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"An issue was discovered in the generator crate before 0.6.18 for Rust. Uninitialized memory is used by Scope, done, and yield_ during API calls.","ecosystems":["crates.io"],"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":"Uninitialized memory use in generator","id":"CVE-2019-16144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":3,"n_references":2,"next":{"headline":"Cross-site scripting in padrino-contrib","id":"CVE-2019-16145"},"packages":[{"ecosystem":"crates.io","fixed":["0.6.18"],"introduced":["0"],"last_affected":[],"package":"generator","purl":null,"source":"GHSA-6c65-xcf5-299x"},{"ecosystem":"crates.io","fixed":["0.6.18"],"introduced":["0"],"last_affected":[],"package":"generator","purl":"pkg:cargo/generator","source":"GHSA-6c65-xcf5-299x"},{"ecosystem":"crates.io","fixed":["0.6.18"],"introduced":["0.0.0-0"],"last_affected":[],"package":"generator","purl":"pkg:cargo/generator","source":"RUSTSEC-2019-0020"}],"prev":{"headline":"Algorithms compute incorrect results in blake2","id":"CVE-2019-16143"},"products":["n/a"],"published":"2019-09-09","related":[],"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":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"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":"Attackers can exploit uninitialized memory in the Rust generator crate to potentially disclose sensitive data or execute arbitrary code.","url":"https://insights.sbomify.com/CVE-2019-16144/"}