Service crash via unchecked tensor rank
Published Jul 30, 2024 · Updated Aug 2, 2024
Denial of service in Google TensorFlow before 2.13.0 allows remote attackers to crash an application via a non-rank-2 tensor. The UpperBound kernel relies on bypassable shape-function validation and accepts values or sorted_inputs tensors that are not rank 2 before reading their dimensions. The application must pass an attacker-controlled tensor to this operation; successful exploitation terminates the process without altering or disclosing data.
Summary
What happened
Denial of service in Google TensorFlow before 2.13.0 allows remote attackers to crash an application via a non-rank-2 tensor. The UpperBound kernel relies on bypassable shape-function validation and accepts values or sorted_inputs tensors that are not rank 2 before reading their dimensions. The application must pass an attacker-controlled tensor to this operation; successful exploitation terminates the process without altering or disclosing data.
The record
- CVE
- CVE-2023-33976
- Published
- Jul 30, 2024
- Updated
- Aug 2, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.13.0
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
No public exploit references are available in this record.
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