Control-utility memory exhaustion via leaked ECU configuration
Published Feb 27, 2023 · Updated Aug 2, 2024
Memory leak in COVESA DLT Daemon 2.18.8 and earlier allows attackers to exhaust control-utility memory during initialization. The set_ecuid function calls dlt_parse_config_param to allocate ecuid_conf, copies its value into local_ecuid, and returns without freeing the allocation. The path is reached when dlt-logstorage-ctrl or dlt-passive-node-ctrl initializes control communication; public sources do not establish daemon-wide failure.
Summary
What happened
Memory leak in COVESA DLT Daemon 2.18.8 and earlier allows attackers to exhaust control-utility memory during initialization. The set_ecuid function calls dlt_parse_config_param to allocate ecuid_conf, copies its value into local_ecuid, and returns without freeing the allocation. The path is reached when dlt-logstorage-ctrl or dlt-passive-node-ctrl initializes control communication; public sources do not establish daemon-wide failure.
The record
- CVE
- CVE-2023-26257
- Published
- Feb 27, 2023
- Updated
- Aug 2, 2024
- Vendor
- COVESA
- Product
- DLT Daemon
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2023CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=0 <=2.18.8
What conditions does exploitation require?
What is affected?
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
- Upstream AddressSanitizer memory-leak 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