{"answers":{"affected":"3 open source packages ship an affected version, including pywasm3. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-28990 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28990 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28990 is a high-severity memory corruption vulnerability in n/a, published on 20 May 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-28990 and fix it if it is affected.\n\nWhat it is: CVE-2022-28990 is a high-severity memory corruption vulnerability in n/a, published on 20 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-28990 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pywasm3 (PyPI): affected all versions up to 0.5.0; no fix listed\n- pywasm3 (PyPI): affected all versions up to 0.5.0; no fix listed\n- pywasm3 (PyPI): affected all versions up to 0.5.0; no fix listed\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-2022-28990/ (Markdown: https://insights.sbomify.com/CVE-2022-28990/index.md)","id":"CVE-2022-28990","markdown":"https://insights.sbomify.com/CVE-2022-28990/index.md","name":"CVE-2022-28990","record":{"aliases":["GHSA-77fq-4xf5-hph4","PYSEC-2022-43154"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WASM3 runtime","requires_auth":"low_privilege","summary":"A heap overflow in the WASM3 library allows attackers to execute arbitrary code or cause denial of service via a malicious WebAssembly file.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wasm3","vendor":"wasm3_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"WASM3 v0.5.0 was discovered to contain a heap overflow via the component /wabt/bin/poc.wasm.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Buffer overflow in wasm3","id":"CVE-2022-28990","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-28991"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.5.0"],"package":"pywasm3","purl":null,"source":"GHSA-77fq-4xf5-hph4"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.5.0"],"package":"pywasm3","purl":"pkg:pypi/pywasm3","source":"GHSA-77fq-4xf5-hph4"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.5.0"],"package":"pywasm3","purl":"pkg:pypi/pywasm3","source":"PYSEC-2022-43154"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2022-28987"},"products":["n/a"],"published":"2022-05-20","related":[{"cvss_score":9.8,"headline":"pywasm3 contains a heap buffer overflow which leads to segmentation fault","id":"CVE-2024-34249","kev_date_added":null,"published":"2024-05-06"},{"cvss_score":8.4,"headline":"pywasm3 has an Invalid Memory Read, Leading to DoS and Potential Code Execution","id":"CVE-2024-27528","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":8.4,"headline":"wasm3 uncontrolled memory allocation vulnerability","id":"CVE-2024-27529","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":8.4,"headline":"pywasm3 contains a Use-After-Free in ForEachModule","id":"CVE-2024-27530","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-27527","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2024-34246","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-03","vendors":["n/a"]},"summary":"A heap overflow in the WASM3 library allows attackers to execute arbitrary code or cause denial of service via a malicious WebAssembly file.","url":"https://insights.sbomify.com/CVE-2022-28990/"}