{"answers":{"affected":"3 open source packages ship an affected version, including internment. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-28037 in the wild and no public exploit code.","fix":"Upgrade internment to 0.4.2 or later.","what":"CVE-2021-28037 is a critical 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-28037 and fix it if it is affected.\n\nWhat it is: CVE-2021-28037 is a critical 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-28037 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- internment (crates.io): affected all versions; fixed in 0.4.2\n- internment (crates.io): affected all versions; fixed in 0.4.2\n- internment (crates.io): affected from 0.0.0-0; fixed in 0.4.2\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-28037/ (Markdown: https://insights.sbomify.com/CVE-2021-28037/index.md)","id":"CVE-2021-28037","markdown":"https://insights.sbomify.com/CVE-2021-28037/index.md","name":"CVE-2021-28037","record":{"aliases":["GHSA-gppw-3h6h-v6q2","RUSTSEC-2021-0036"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust internment crate","requires_auth":"none","summary":"A data race in the Rust internment crate can lead to memory corruption, potentially allowing arbitrary code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"internment","vendor":"internment_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":[],"description":"An issue was discovered in the internment crate before 0.4.2 for Rust. There is a data race that can cause memory corruption because of the unconditional implementation of Sync for Intern\u003cT\u003e.","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":"Data race in internment","id":"CVE-2021-28037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2021"},"n_packages":3,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2021-28038"},"packages":[{"ecosystem":"crates.io","fixed":["0.4.2"],"introduced":["0"],"last_affected":[],"package":"internment","purl":null,"source":"GHSA-gppw-3h6h-v6q2"},{"ecosystem":"crates.io","fixed":["0.4.2"],"introduced":["0"],"last_affected":[],"package":"internment","purl":"pkg:cargo/internment","source":"GHSA-gppw-3h6h-v6q2"},{"ecosystem":"crates.io","fixed":["0.4.2"],"introduced":["0.0.0-0"],"last_affected":[],"package":"internment","purl":"pkg:cargo/internment","source":"RUSTSEC-2021-0036"}],"prev":{"headline":"quinn invalidly assumes the memory layout of std::net::SocketAddr","id":"CVE-2021-28036"},"products":["n/a"],"published":"2021-03-05","related":[{"cvss_score":8.1,"headline":"Use after free in internment","id":"CVE-2020-35874","kev_date_added":null,"published":"2020-12-31"}],"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":"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 data race in the Rust internment crate can lead to memory corruption, potentially allowing arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2021-28037/"}