Process crash via zero ResourceScatterDiv updates
Published Aug 12, 2021 · Updated Aug 4, 2024
Divide-by-zero in Google TensorFlow ResourceScatterDiv before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 allows local users to crash a process. The CPU kernel shares a common binary-operation path and executes division without first rejecting zero values in the updates tensor. An attacker-controlled invocation of the operation is required, and the reported consequence is limited to a crash of the hosting process.
Summary
What happened
Divide-by-zero in Google TensorFlow ResourceScatterDiv before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 allows local users to crash a process. The CPU kernel shares a common binary-operation path and executes division without first rejecting zero values in the updates tensor. An attacker-controlled invocation of the operation is required, and the reported consequence is limited to a crash of the hosting process.
The record
- CVE
- CVE-2021-37642
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-369, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2021CVE 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=< 2.3.4
- Affected versionversion=>= 2.4.0, < 2.4.3
- Affected versionversion=>= 2.5.0, < 2.5.1
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
- ResourceScatterDiv zero-update proof of conceptproof 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