Process hang via skipped ellipsis-loop increments
Published Aug 12, 2021 · Updated Nov 13, 2024
Denial of service in Google TensorFlow Lite 2.6.0rc0 through 2.6.0rc1 allows local users to hang a process with a crafted model. In the strided-slice ellipsis path, an ellipsis_end_idx below the loop index bypasses both increments because continue skips the outer increment. Processing such a model is required, and the resulting infinite loop consumes CPU and stalls that TensorFlow Lite process without reported data access or modification.
Summary
What happened
Denial of service in Google TensorFlow Lite 2.6.0rc0 through 2.6.0rc1 allows local users to hang a process with a crafted model. In the strided-slice ellipsis path, an ellipsis_end_idx below the loop index bypasses both increments because continue skips the outer increment. Processing such a model is required, and the resulting infinite loop consumes CPU and stalls that TensorFlow Lite process without reported data access or modification.
The record
- CVE
- CVE-2021-37686
- Published
- Aug 12, 2021
- Updated
- Nov 13, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-835, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2021CVE publishedPublication date reported by the CVE source.
- Nov 13, 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.6.0rc0, < 2.6.0rc2
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