{"answers":{"affected":"5 open source packages ship an affected version, including flumedb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-45684 in the wild and no public exploit code.","fix":"Upgrade flumedb to 0.1.6 or later.","what":"CVE-2021-45684 is a critical vulnerability in n/a, published on 26 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-45684 and fix it if it is affected.\n\nWhat it is: CVE-2021-45684 is a critical vulnerability in n/a, published on 26 Dec 2021. 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-2021-45684 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- flumedb (crates.io): affected all versions; fixed in 0.1.6\n- flumedb (crates.io): affected all versions; fixed in 0.1.6\n- flumedb (crates.io): affected all versions; fixed in 0.1.6\n- flumedb (crates.io): affected all versions; fixed in 0.1.6\n- flumedb (crates.io): affected from 0.0.0-0; fixed in 0.1.6\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-2021-45684/ (Markdown: https://insights.sbomify.com/CVE-2021-45684/index.md)","id":"CVE-2021-45684","markdown":"https://insights.sbomify.com/CVE-2021-45684/index.md","name":"CVE-2021-45684","record":{"aliases":["GHSA-p46c-w9m3-7qr2","GHSA-p56p-gq3f-whg8","RUSTSEC-2021-0086"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust flumedb crate","requires_auth":"none","summary":"An attacker can read uninitialized memory via the read_entry function in the flumedb Rust crate, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flumedb","vendor":"flumedb_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-908","name":"Use of Uninitialized Resource"}],"description":"An issue was discovered in the flumedb crate through 2021-01-07 for Rust. read_entry may read from uninitialized memory locations.","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":"Use of Uninitialized Resource in flumedb.","id":"CVE-2021-45684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":5,"n_references":2,"next":{"headline":"columnar: Read on uninitialized buffer may cause UB (ColumnarReadExt::read_typed_vec())","id":"CVE-2021-45685"},"packages":[{"ecosystem":"crates.io","fixed":["0.1.6"],"introduced":["0"],"last_affected":[],"package":"flumedb","purl":null,"source":"GHSA-p46c-w9m3-7qr2"},{"ecosystem":"crates.io","fixed":["0.1.6"],"introduced":["0"],"last_affected":[],"package":"flumedb","purl":"pkg:cargo/flumedb","source":"GHSA-p46c-w9m3-7qr2"},{"ecosystem":"crates.io","fixed":["0.1.6"],"introduced":["0"],"last_affected":[],"package":"flumedb","purl":null,"source":"GHSA-p56p-gq3f-whg8"},{"ecosystem":"crates.io","fixed":["0.1.6"],"introduced":["0"],"last_affected":[],"package":"flumedb","purl":"pkg:cargo/flumedb","source":"GHSA-p56p-gq3f-whg8"},{"ecosystem":"crates.io","fixed":["0.1.6"],"introduced":["0.0.0-0"],"last_affected":[],"package":"flumedb","purl":"pkg:cargo/flumedb","source":"RUSTSEC-2021-0086"}],"prev":{"headline":"'Read' on uninitialized memory may cause UB","id":"CVE-2021-45683"},"products":["n/a"],"published":"2021-12-26","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-04","vendors":["n/a"]},"summary":"An attacker can read uninitialized memory via the read_entry function in the flumedb Rust crate, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2021-45684/"}