Memory leak via overwritten stroke-dash array allocations
Published Jan 20, 2023 · Updated Apr 3, 2025
Memory leak in GPAC 2.2-rev0-gab012bbfb-master allows local users to consume process memory by opening a crafted LASeR file. In lsr_read_rare_full, each parsed stroke-dash array replaced the vals and units pointers with new allocations without releasing the prior buffers. User interaction is required to process the file; the published proof of concept demonstrates a 220-byte leak, not a crash.
Summary
What happened
Memory leak in GPAC 2.2-rev0-gab012bbfb-master allows local users to consume process memory by opening a crafted LASeR file. In lsr_read_rare_full, each parsed stroke-dash array replaced the vals and units pointers with new allocations without releasing the prior buffers. User interaction is required to process the file; the published proof of concept demonstrates a 220-byte leak, not a crash.
The record
- CVE
- CVE-2023-23145
- Published
- Jan 20, 2023
- Updated
- Apr 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2023CVE publishedPublication date reported by the CVE source.
- Apr 3, 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
- memory_leak_lsr_read_rare_full proof of conceptproof of concept · demonstrated
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