{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-18378 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2020-18378 is a medium-severity vulnerability in n/a, published on 22 Aug 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-18378 and fix it if it is affected.\n\nWhat it is: CVE-2020-18378 is a medium-severity vulnerability in n/a, published on 22 Aug 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-18378 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-2020-18378/ (Markdown: https://insights.sbomify.com/CVE-2020-18378/index.md)","id":"CVE-2020-18378","markdown":"https://insights.sbomify.com/CVE-2020-18378/index.md","name":"CVE-2020-18378","record":{"aliases":["DEBIAN-CVE-2020-18378","GHSA-vj54-ff4j-gq2v","UBUNTU-CVE-2020-18378"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Binaryen WebAssembly library","requires_auth":"none","summary":"A crafted WebAssembly input triggers a null pointer dereference in Binaryen, causing a segmentation fault and denial of service.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"binaryen","vendor":"webassembly"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"A NULL pointer dereference was discovered in SExpressionWasmBuilder::makeBlock in wasm/wasm-s-parser.c in Binaryen 1.38.26. A crafted wasm input can cause a segmentation fault, leading to denial-of-service, as demonstrated by wasm-as.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Null dereference in n/a","id":"CVE-2020-18378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-18382"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-18336"},"products":["n/a"],"published":"2023-08-22","related":[{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2020-18382","kev_date_added":null,"published":"2023-08-22"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2019-15758","kev_date_added":null,"published":"2019-08-29"},{"cvss_score":6.5,"headline":"Null dereference in n/a","id":"CVE-2019-15759","kev_date_added":null,"published":"2019-08-29"},{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2019-7700","kev_date_added":null,"published":"2019-02-10"},{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2019-7701","kev_date_added":null,"published":"2019-02-10"},{"cvss_score":6.5,"headline":"Null dereference in n/a","id":"CVE-2019-7702","kev_date_added":null,"published":"2019-02-10"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-03","vendors":["n/a"]},"summary":"A crafted WebAssembly input triggers a null pointer dereference in Binaryen, causing a segmentation fault and denial of service.","url":"https://insights.sbomify.com/CVE-2020-18378/"}