Process memory growth via leaked integer copies
Published May 9, 2023 · Updated Jan 29, 2025
Memory leak in yasm 1.3.0 allows local users to increase process memory use by supplying assembly input that triggers integer copies. The yasm_intnum_copy function in libyasm/intnum.c fails to release memory associated with copied integer objects during input processing. Triggering requires a user to process crafted input; the upstream security policy treats inputs as trusted, and Debian records no security impact.
Summary
What happened
Memory leak in yasm 1.3.0 allows local users to increase process memory use by supplying assembly input that triggers integer copies. The yasm_intnum_copy function in libyasm/intnum.c fails to release memory associated with copied integer objects during input processing. Triggering requires a user to process crafted input; the upstream security policy treats inputs as trusted, and Debian records no security impact.
The record
- CVE
- CVE-2023-31975
- Published
- May 9, 2023
- Updated
- Jan 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- yasm issue 210 memory-leak reproducerproof of concept · unverified
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