{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34251 exists.","fix":"No fix has been published for CVE-2024-34251 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-34251 is a high-severity memory corruption vulnerability in n/a, published on 6 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-34251 and fix it if it is affected.\n\nWhat it is: CVE-2024-34251 is a high-severity memory corruption vulnerability in n/a, published on 6 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34251 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2024-34251/ (Markdown: https://insights.sbomify.com/CVE-2024-34251/index.md)","id":"CVE-2024-34251","markdown":"https://insights.sbomify.com/CVE-2024-34251/index.md","name":"CVE-2024-34251","record":{"aliases":["GHSA-v4vq-27w6-p28p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WebAssembly runtime library","requires_auth":"none","summary":"A remote attacker can cause a denial of service in the wasm-micro-runtime library via an out-of-bounds memory read.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"webassembly_micro_runtime","vendor":"bytecodealliance"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-125","name":"Out-of-bounds Read"}],"description":"An out-of-bound memory read vulnerability was discovered in Bytecode Alliance wasm-micro-runtime v2.0.0 which allows a remote attacker to cause a denial of service via the \"block_type_get_arity\" function in core/iwasm/interpreter/wasm.h.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Memory corruption in n/a","id":"CVE-2024-34251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"pywasm3 contains a global buffer overflow which leads to segmentation fault","id":"CVE-2024-34252"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-34250"},"products":["n/a"],"published":"2024-05-06","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2024-25431","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2024-27532","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2023-48105","kev_date_added":null,"published":"2023-11-22"},{"cvss_score":7,"headline":"iwasm vulnerable to filesystem sandbox escape with symlink when using uvwasi feature","id":"CVE-2025-43853","kev_date_added":null,"published":"2025-05-15"},{"cvss_score":6.9,"headline":"WebAssembly Micro Runtime's `--addr-pool` option allows all IPv4 addresses when subnet mask is not specified","id":"CVE-2025-54126","kev_date_added":null,"published":"2025-07-29"},{"cvss_score":6.2,"headline":"Memory corruption in n/a","id":"CVE-2024-34250","kev_date_added":null,"published":"2024-05-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"A remote attacker can cause a denial of service in the wasm-micro-runtime library via an out-of-bounds memory read.","url":"https://insights.sbomify.com/CVE-2024-34251/"}