Service interruption via unreleased action strings
Published Feb 26, 2024 · Updated Aug 9, 2024
Memory leak in listaction.c in LibMing 0.4.8 allows remote authenticated users to interrupt service via repeated action-record processing. In printActionRecord, printf consumes a heap string returned by readString, but the caller discards the pointer without releasing its malloc allocation. The affected path must be invoked repeatedly through an application that exposes it; unreleased strings accumulate and can exhaust memory in that process.
Summary
What happened
Memory leak in listaction.c in LibMing 0.4.8 allows remote authenticated users to interrupt service via repeated action-record processing. In printActionRecord, printf consumes a heap string returned by readString, but the caller discards the pointer without releasing its malloc allocation. The affected path must be invoked repeatedly through an application that exposes it; unreleased strings accumulate and can exhaust memory in that process.
The record
- CVE
- CVE-2024-25770
- Published
- Feb 26, 2024
- Updated
- Aug 9, 2024
- Vendor
- Ming Development Team
- Product
- LibMing
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 9, 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.
- Affected versionversion=0.4.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- LibMing listaction.c memory-leak demonstrationproof 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