Quick answers
- Is CVE-2024-27528 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-27528 being exploited in the wild.
- How severe is CVE-2024-27528?
- High severity, with a CVSS score of 8.4, published 9 November 2024.
- Which products and versions are affected?
- pywasm3 (PyPI) <= 0.5.0, ECOSYSTEM:introduced=0,last_affected=0.5.0, ECOSYSTEM:introduced=0,last_affected=139076a.
- Is there a fix for CVE-2024-27528?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2024-27528 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2024-27528?
- Check whether you run pywasm3 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds (invalid) memory read vulnerability exists in the Wasm3 interpreter (specifically version 139076a and pywasm3 <= 0.5.0). The flaw is located in the execution engine, specifically within the 'op_Select_i32_ssr' function in 'm3_exec.h'. An attacker can exploit this by providing a malformed WebAssembly file that triggers an invalid memory dereference during validation or execution. This can result in a segmentation fault (DoS) or potentially be leveraged for arbitrary code execution. While the CVSS vector indicates local access, the vulnerability is triggered by the content of the loaded WASM module.
Affected products
- wasm3 pywasm3 <= 0.5.0
- wasm3 wasm3 139076a
Identifiers
- CVE-2024-27528
- GHSA-mhg9-mm8c-c683
- PYSEC-2024-304
Timeline
- 2024-02-19: disclosed: Issue reported on GitHub repository
- 2024-11-08: advisory: NVD published CVE-2024-27528
- 2024-11-09: advisory: GitHub Advisory published