Memory exhaustion via unreleased delimited-message allocations
Published Dec 2, 2024 · Updated Dec 2, 2024
Memory leak in Nanopb 0.4.0 through 0.4.9 allows remote authenticated users to interrupt services via malformed delimited messages. In pb_decode_ex(), a failed pb_close_string_substream() returned before the PB_ENABLE_MALLOC cleanup path, so pb_release() never freed FT_POINTER allocations. The path requires malloc support, an FT_POINTER field, an unknown-length custom stream, PB_DECODE_DELIMITED, and a corrupted length prefix; repeated failures can exhaust memory.
Summary
What happened
Memory leak in Nanopb 0.4.0 through 0.4.9 allows remote authenticated users to interrupt services via malformed delimited messages. In pb_decode_ex(), a failed pb_close_string_substream() returned before the PB_ENABLE_MALLOC cleanup path, so pb_release() never freed FT_POINTER allocations. The path requires malloc support, an FT_POINTER field, an unknown-length custom stream, PB_DECODE_DELIMITED, and a corrupted length prefix; repeated failures can exhaust memory.
The record
- CVE
- CVE-2024-53984
- Published
- Dec 2, 2024
- Updated
- Dec 2, 2024
- Vendor
- Petteri Aimonen
- Product
- Nanopb
- Classifications
- CWE-755, CWE-401, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Dec 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.4.0, < 0.4.9.1
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
No public exploit references are available in this record.
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