Undefined behavior via unchecked empty node range
Published Aug 12, 2021 · Updated Aug 4, 2024
Undefined behavior in Google TensorFlow before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 allows local users to disrupt execution. The boosted-tree gain and split kernels index node_id_range as a two-element vector without first rejecting an empty or incorrectly shaped tensor, binding a reference to null. Exploitation requires local ability to execute a TensorFlow graph, and the published advisory does not specify the resulting effect beyond undefined behavior.
Summary
What happened
Undefined behavior in Google TensorFlow before 2.3.4, 2.4.0 through 2.4.2, and 2.5.0 allows local users to disrupt execution. The boosted-tree gain and split kernels index node_id_range as a two-element vector without first rejecting an empty or incorrectly shaped tensor, binding a reference to null. Exploitation requires local ability to execute a TensorFlow graph, and the published advisory does not specify the resulting effect beyond undefined behavior.
The record
- CVE
- CVE-2021-37662
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-824
- 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.
Weakness, pattern, technique
Public exploit references
- Boosted-tree empty node_id_range 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