CVE-2022-26477
Description
The Security Team noticed that the termination condition of the for loop in the readExternal method is a controllable variable, which, if tampered with, may lead to CPU exhaustion. As a fix, we added an upper bound and termination condition in the read and write logic. We classify it as a "low-priority but useful improvement". SystemDS is a distributed system and needs to serialize/deserialize data but in many code paths (e.g., on Spark broadcast/shuffle or writing to sequence files) the byte stream is anyway protected by additional CRC fingerprints. In this particular case though, the number of decoders is upper-bounded by twice the number of columns, which means an attacker would need to modify two entries in the byte stream in a consistent manner. By adding these checks robustness was strictly improved with almost zero overhead. These code changes are available in versions higher than 2.2.1.
How to fix
- org.apache.systemds:systemds2.2.2 or later
- systemds2.2.2 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| apache systemds | v ≤ 2.2.1 | — |
| org.apache.systemds:systemdsMaven | v < 2.2.2 | 2.2.2 |
| systemdsPyPI | v < 2.2.2 | 2.2.2 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.