CPU exhaustion via controllable deserialization loop bound
Published Jun 27, 2022 · Updated Aug 3, 2024
Uncontrolled resource consumption in Apache SystemDS before 2.2.2 allows remote attackers to exhaust CPU through crafted serialized data. The readExternal method uses a byte-stream value as a loop termination bound, so a manipulated decoder count drives excessive iteration. Exploitation requires consistent alteration of two stream entries, while CRC protection limits many Spark and sequence-file paths; successful input consumes CPU and interrupts processing.
Summary
What happened
Uncontrolled resource consumption in Apache SystemDS before 2.2.2 allows remote attackers to exhaust CPU through crafted serialized data. The readExternal method uses a byte-stream value as a loop termination bound, so a manipulated decoder count drives excessive iteration. Exploitation requires consistent alteration of two stream entries, while CRC protection limits many Spark and sequence-file paths; successful input consumes CPU and interrupts processing.
The record
- CVE
- CVE-2022-26477
- Published
- Jun 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache SystemDS
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <2.2.2
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