Process crash or CPU exhaustion via unsafe deserialization
Published Jan 31, 2020 · Updated Aug 4, 2024
Denial of service in MessagePack for C# packages before 1.9.11 and 2.0.0 through 2.1.89 allows attackers to crash or exhaust a process. Built-in and custom formatters omit bounded-depth handling for nested objects and collision-resistant comparers for attacker-controlled hash keys. Reachability requires an application to deserialize untrusted MessagePack data; deep object graphs crash the process, while colliding keys consume excessive CPU.
Summary
What happened
Denial of service in MessagePack for C# packages before 1.9.11 and 2.0.0 through 2.1.89 allows attackers to crash or exhaust a process. Built-in and custom formatters omit bounded-depth handling for nested objects and collision-resistant comparers for attacker-controlled hash keys. Reachability requires an application to deserialize untrusted MessagePack data; deep object graphs crash the process, while colliding keys consume excessive CPU.
The record
- CVE
- CVE-2020-5234
- Published
- Jan 31, 2020
- Updated
- Aug 4, 2024
- Vendor
- MessagePack-CSharp
- Product
- MessagePack.ReactiveProperty
- Classifications
- CWE-787, CWE-121, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2020CVE 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=< 1.9.11
- Affected versionversion=>= 2.0.0, < 2.1.90
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
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