CVE-2023-51258Public exploit

Resource exhaustion via unreleased token buffers

Published Jan 18, 2024 · Updated Aug 2, 2024

Memory leakage in Yasm 1.3.0 allows local users to consume process memory by assembling a crafted NASM-syntax input file. The new_Token routine allocates text buffers during tokenization and macro expansion without releasing 49 bytes across 14 allocations in the published reproducer. Reaching the condition requires local execution of Yasm on the file; upstream and Linux distributors dispute security impact because the demonstrated leak is small and ends with the CLI process.

CVSS severity5.5
Medium
EPSS probability0.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory leakage in Yasm 1.3.0 allows local users to consume process memory by assembling a crafted NASM-syntax input file. The new_Token routine allocates text buffers during tokenization and macro expansion without releasing 49 bytes across 14 allocations in the published reproducer. Reaching the condition requires local execution of Yasm on the file; upstream and Linux distributors dispute security impact because the demonstrated leak is small and ends with the CLI process.

The record

CVE
CVE-2023-51258
Published
Jan 18, 2024
Updated
Aug 2, 2024
Vendor
Tortall Networks
Product
Yasm
Classifications
CWE-401, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jan 18, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.3.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Tortall Networks · Yasmversion=1.3.0

Published CVSS scores

2.8SUSECVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
5.5CISA-ADPCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-401Missing Release of Memory after Effective Lifetime
T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo