Process crash via unchecked null charset result
Published Aug 24, 2021 · Updated Aug 4, 2024
Improper exception handling in Sonicdoe detect-character-encoding 0.6.0 and earlier allows attackers to crash a Node.js process via unmatched input. The DetectCharacterEncoding native wrapper passes a null result from ICU's ucsdet_detect function to ucsdet_getName without checking it, causing a segmentation fault. Exploitation requires a consuming application to pass attacker-controlled bytes to the library; the resulting crash interrupts that Node.js service.
Summary
What happened
Improper exception handling in Sonicdoe detect-character-encoding 0.6.0 and earlier allows attackers to crash a Node.js process via unmatched input. The DetectCharacterEncoding native wrapper passes a null result from ICU's ucsdet_detect function to ucsdet_getName without checking it, causing a segmentation fault. Exploitation requires a consuming application to pass attacker-controlled bytes to the library; the resulting crash interrupts that Node.js service.
The record
- CVE
- CVE-2021-39157
- Published
- Aug 24, 2021
- Updated
- Aug 4, 2024
- Vendor
- Sonicdoe
- Product
- detect-character-encoding
- Classifications
- CWE-755, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 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.7.0
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
- Upstream Express crash 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