Process crash via unchecked tensor ranks
Published May 14, 2021 · Updated Oct 31, 2024
Improper input validation in Google TensorFlow 2.4.0 and 2.4.1 allows local users to crash the process with malformed tensors. The QuantizeAndDequantizeV4GradientOp kernel accepts rank-two input_min or input_max tensors and passes them to vec(), whose rank-one requirement terminates execution with a CHECK failure. Exploitation requires local code execution that invokes the raw operation; it interrupts only the hosting process, with no reported data disclosure or modification.
Summary
What happened
Improper input validation in Google TensorFlow 2.4.0 and 2.4.1 allows local users to crash the process with malformed tensors. The QuantizeAndDequantizeV4GradientOp kernel accepts rank-two input_min or input_max tensors and passes them to vec(), whose rank-one requirement terminates execution with a CHECK failure. Exploitation requires local code execution that invokes the raw operation; it interrupts only the hosting process, with no reported data disclosure or modification.
The record
- CVE
- CVE-2021-29544
- Published
- May 14, 2021
- Updated
- Oct 31, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-754, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2021CVE publishedPublication date reported by the CVE source.
- Oct 31, 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=>= 2.4.0, < 2.4.2
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 QuantizeAndDequantizeV4Grad crash reproducerproof 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