{"answers":{"affected":"3 open source packages ship an affected version, including byte_struct. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-28033 in the wild and no public exploit code.","fix":"Upgrade byte_struct to 0.6.1 or later.","what":"CVE-2021-28033 is a critical memory corruption vulnerability in n/a, published on 5 Mar 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-28033 and fix it if it is affected.\n\nWhat it is: CVE-2021-28033 is a critical memory corruption vulnerability in n/a, published on 5 Mar 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-28033 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- byte_struct (crates.io): affected all versions; fixed in 0.6.1\n- byte_struct (crates.io): affected all versions; fixed in 0.6.1\n- byte_struct (crates.io): affected from 0.0.0-0; fixed in 0.6.1\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-28033/ (Markdown: https://insights.sbomify.com/CVE-2021-28033/index.md)","id":"CVE-2021-28033","markdown":"https://insights.sbomify.com/CVE-2021-28033/index.md","name":"CVE-2021-28033","record":{"aliases":["GHSA-8fgg-5v78-6g76","RUSTSEC-2021-0032"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust byte_struct crate","requires_auth":"none","summary":"A panic during deserialization in the byte_struct crate can cause a drop of uninitialized memory, potentially leading to crashes or undefined behavior.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"byte_struct","vendor":"byte_struct_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 byte_struct crate before 0.6.1 for Rust. There can be a drop of uninitialized memory if a certain deserialization method panics.","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":"Deserializing an array can free uninitialized memory in byte_struct","id":"CVE-2021-28033","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"Double free in stack_dst","id":"CVE-2021-28034"},"packages":[{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0"],"last_affected":[],"package":"byte_struct","purl":null,"source":"GHSA-8fgg-5v78-6g76"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0"],"last_affected":[],"package":"byte_struct","purl":"pkg:cargo/byte_struct","source":"GHSA-8fgg-5v78-6g76"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"byte_struct","purl":"pkg:cargo/byte_struct","source":"RUSTSEC-2021-0032"}],"prev":{"headline":"Use after free in nano_arena","id":"CVE-2021-28032"},"products":["n/a"],"published":"2021-03-05","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-03","vendors":["n/a"]},"summary":"A panic during deserialization in the byte_struct crate can cause a drop of uninitialized memory, potentially leading to crashes or undefined behavior.","url":"https://insights.sbomify.com/CVE-2021-28033/"}