Local memory consumption via unreleased ASDU allocation
Published Feb 24, 2023 · Updated Mar 12, 2025
Memory leak in lib60870 2.3.2 allows local users to consume unreleased memory when the example multi-client server exits. At line 213, main assigns a CS101_ASDU_create allocation to newAsdu but never releases that object before shutdown. The published Ctrl+C reproduction requires local process control and demonstrates one 296-byte leak at exit, not sustained remote exhaustion.
Summary
What happened
Memory leak in lib60870 2.3.2 allows local users to consume unreleased memory when the example multi-client server exits. At line 213, main assigns a CS101_ASDU_create allocation to newAsdu but never releases that object before shutdown. The published Ctrl+C reproduction requires local process control and demonstrates one 296-byte leak at exit, not sustained remote exhaustion.
The record
- CVE
- CVE-2023-23205
- Published
- Feb 24, 2023
- Updated
- Mar 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 24, 2023CVE publishedPublication date reported by the CVE source.
- Mar 12, 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
- AddressSanitizer Ctrl+C reproductionproof 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