{"answers":{"affected":"5 open source packages ship an affected version, including vm-memory. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-13759 in the wild and no public exploit code.","fix":"Upgrade vm-memory to a fixed version for your release line: 0.1.1 or 0.2.1.","what":"CVE-2020-13759 is a high-severity vulnerability in n/a, published on 2 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-13759 and fix it if it is affected.\n\nWhat it is: CVE-2020-13759 is a high-severity vulnerability in n/a, published on 2 Jun 2020. 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-2020-13759 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vm-memory (crates.io): affected all versions; fixed in 0.1.1\n- vm-memory (crates.io): affected all versions; fixed in 0.1.1\n- vm-memory (crates.io): affected from 0.0.0-0; fixed in 0.1.1, 0.2.1\n- vm-memory (crates.io): affected from 0.2.0; fixed in 0.2.1\n- vm-memory (crates.io): affected from 0.2.0; fixed in 0.2.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-2020-13759/ (Markdown: https://insights.sbomify.com/CVE-2020-13759/index.md)","id":"CVE-2020-13759","markdown":"https://insights.sbomify.com/CVE-2020-13759/index.md","name":"CVE-2020-13759","record":{"aliases":["GHSA-mm4m-qg48-f7wc","RUSTSEC-2020-0157"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust memory library","requires_auth":"none","summary":"Attackers can cause denial of service by exploiting improper memory access in the rust-vmm vm-memory library.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vm-memory","vendor":"vm-memory_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"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"rust-vmm vm-memory before 0.1.1 and 0.2.x before 0.2.1 allows attackers to cause a denial of service (loss of IP networking) because read_obj and write_obj do not properly access memory. This affects aarch64 (with musl or glibc) and x86_64 (with musl).","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":"Improper Synchronization and Race Condition in vm-memory","id":"CVE-2020-13759","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":5,"n_references":3,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-13760"},"packages":[{"ecosystem":"crates.io","fixed":["0.1.1"],"introduced":["0"],"last_affected":[],"package":"vm-memory","purl":null,"source":"GHSA-mm4m-qg48-f7wc"},{"ecosystem":"crates.io","fixed":["0.1.1"],"introduced":["0"],"last_affected":[],"package":"vm-memory","purl":"pkg:cargo/vm-memory","source":"GHSA-mm4m-qg48-f7wc"},{"ecosystem":"crates.io","fixed":["0.1.1","0.2.1"],"introduced":["0.0.0-0","0.2.0-0"],"last_affected":[],"package":"vm-memory","purl":"pkg:cargo/vm-memory","source":"RUSTSEC-2020-0157"},{"ecosystem":"crates.io","fixed":["0.2.1"],"introduced":["0.2.0"],"last_affected":[],"package":"vm-memory","purl":null,"source":"GHSA-mm4m-qg48-f7wc"},{"ecosystem":"crates.io","fixed":["0.2.1"],"introduced":["0.2.0"],"last_affected":[],"package":"vm-memory","purl":"pkg:cargo/vm-memory","source":"GHSA-mm4m-qg48-f7wc"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-13758"},"products":["n/a"],"published":"2020-06-02","related":[{"cvss_score":2.5,"headline":"Default functions in VolatileMemory trait lack bounds checks in vm-memory","id":"CVE-2023-41051","kev_date_added":null,"published":"2023-09-01"}],"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":"Attackers can cause denial of service by exploiting improper memory access in the rust-vmm vm-memory library.","url":"https://insights.sbomify.com/CVE-2020-13759/"}