# CVE-2023-51258: Denial of service in n/a

> A local attacker can cause a denial of service in the YASM assembler via a memory leak in the new_Token function.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jan 2024
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-33896, AZL-35384, DEBIAN-CVE-2023-51258, GHSA-8wwj-vq54-xqww, JLSEC-2026-599, UBUNTU-CVE-2023-51258

## What is CVE-2023-51258?

CVE-2023-51258 is a medium-severity denial of service vulnerability in n/a, published on 18 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A memory leak issue discovered in YASM v.1.3.0 allows a local attacker to cause a denial of service via the new_Token function in the modules/preprocs/nasm/nasm-pp:1512.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2023-51258?

It affects 1 product.


Products: Tortall Yasm.

## How do I fix CVE-2023-51258?

Apply the vendor's patch.

## Is CVE-2023-51258 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51258 exists.

## Other vulnerabilities in n/a

- [CVE-2023-31973](https://insights.sbomify.com/CVE-2023-31973/): Use after free in n/a (high 7.8)
- [CVE-2023-31972](https://insights.sbomify.com/CVE-2023-31972/): Use after free in n/a (medium 5.5)
- [CVE-2023-31974](https://insights.sbomify.com/CVE-2023-31974/): Use after free in n/a (medium 5.5)
- [CVE-2021-33454](https://insights.sbomify.com/CVE-2021-33454/): Null dereference in n/a (medium 5.5)
- [CVE-2021-33455](https://insights.sbomify.com/CVE-2021-33455/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51258 and fix it if it is affected.

What it is: CVE-2023-51258 is a medium-severity denial of service vulnerability in n/a, published on 18 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51258 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-51258/ (Markdown: https://insights.sbomify.com/CVE-2023-51258/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-51258
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-51258
- OSV: https://osv.dev/vulnerability/CVE-2023-51258

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-51258/
Summaries are generated and may contain mistakes; the official description above is the record.