{"answers":{"affected":"3 open source packages ship an affected version, including spin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16137 in the wild and no public exploit code.","fix":"Upgrade spin to 0.5.2 or later.","what":"CVE-2019-16137 is a high-severity 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-16137 and fix it if it is affected.\n\nWhat it is: CVE-2019-16137 is a high-severity 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-16137 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- spin (crates.io): affected all versions; fixed in 0.5.2\n- spin (crates.io): affected all versions; fixed in 0.5.2\n- spin (crates.io): affected from 0.0.0-0; fixed in 0.5.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-2019-16137/ (Markdown: https://insights.sbomify.com/CVE-2019-16137/index.md)","id":"CVE-2019-16137","markdown":"https://insights.sbomify.com/CVE-2019-16137/index.md","name":"CVE-2019-16137","record":{"aliases":["DEBIAN-CVE-2019-16137","GHSA-hv7x-f3pv-gpwr","RUSTSEC-2019-0013"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust spin crate","requires_auth":"none","summary":"A race condition in the Rust spin crate allows two writers to acquire a lock simultaneously, violating mutual exclusion and potentially causing data corruption.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"spin-rs","vendor":"spin-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-662","name":"Improper Synchronization"}],"description":"An issue was discovered in the spin crate before 0.5.2 for Rust, when RwLock is used. Because memory ordering is mishandled, two writers can acquire the lock at the same time, violating mutual exclusion.","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":"Wrong memory orderings violates mutual exclusion in spin","id":"CVE-2019-16137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2019"},"n_packages":3,"n_references":1,"next":{"headline":"Use after free in image","id":"CVE-2019-16138"},"packages":[{"ecosystem":"crates.io","fixed":["0.5.2"],"introduced":["0"],"last_affected":[],"package":"spin","purl":null,"source":"GHSA-hv7x-f3pv-gpwr"},{"ecosystem":"crates.io","fixed":["0.5.2"],"introduced":["0"],"last_affected":[],"package":"spin","purl":"pkg:cargo/spin","source":"GHSA-hv7x-f3pv-gpwr"},{"ecosystem":"crates.io","fixed":["0.5.2"],"introduced":["0.0.0-0"],"last_affected":[],"package":"spin","purl":"pkg:cargo/spin","source":"RUSTSEC-2019-0013"}],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-16133"},"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":"A race condition in the Rust spin crate allows two writers to acquire a lock simultaneously, violating mutual exclusion and potentially causing data corruption.","url":"https://insights.sbomify.com/CVE-2019-16137/"}