Application outage via unclosed ICU charset detector
Published Aug 31, 2021 · Updated Aug 4, 2024
Memory leak in Sonicdoe detect-character-encoding 0.3.0 and earlier allows attackers to exhaust a consuming application's memory. The DetectCharacterEncoding method opens an ICU charsetDetector but fails to call ucsdet_close on successful and error-return paths, retaining its storage after each invocation. Repeated invocation can exhaust the hosting Node.js process; network reachability depends on a consuming program exposing the library.
Summary
What happened
Memory leak in Sonicdoe detect-character-encoding 0.3.0 and earlier allows attackers to exhaust a consuming application's memory. The DetectCharacterEncoding method opens an ICU charsetDetector but fails to call ucsdet_close on successful and error-return paths, retaining its storage after each invocation. Repeated invocation can exhaust the hosting Node.js process; network reachability depends on a consuming program exposing the library.
The record
- CVE
- CVE-2021-39176
- Published
- Aug 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- Sonicdoe
- Product
- detect-character-encoding
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.3.1
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
- GitHub advisory memory-exhaustion 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