Division by zero via unchecked quantized inputs
Published May 14, 2021 · Updated Aug 3, 2024
Divide-by-zero in TensorFlow QuantizedBatchNormWithGlobalNormalization allows local users to cause denial of service via crafted tensor inputs. The kernel reads required scalar elements without validating that input tensors are non-empty, so malformed quantized parameters reach a division-by-zero path and raise a runtime failure. Exploitation requires local code execution in a process using an affected TensorFlow build; the documented consequence is process-level denial of service, not data disclosure or modification.
Summary
What happened
Divide-by-zero in TensorFlow QuantizedBatchNormWithGlobalNormalization allows local users to cause denial of service via crafted tensor inputs. The kernel reads required scalar elements without validating that input tensors are non-empty, so malformed quantized parameters reach a division-by-zero path and raise a runtime failure. Exploitation requires local code execution in a process using an affected TensorFlow build; the documented consequence is process-level denial of service, not data disclosure or modification.
The record
- CVE
- CVE-2021-29548
- Published
- May 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-369, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2021CVE 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=< 2.1.4
- Affected versionversion=>= 2.2.0, < 2.2.3
- Affected versionversion=>= 2.3.0, < 2.3.3
- 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.
Public exploit references
- QuantizedBatchNormWithGlobalNormalization division-by-zero 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