Process crash via RaggedRange size overflow
Published Sep 16, 2022 · Updated Apr 23, 2025
Integer overflow in Google TensorFlow before 2.7.2, 2.8.0, and 2.9.0 allows remote attackers to crash the process via limits. RaggedRangeOp computes ceil(abs((limit - start) / delta)) as a floating-point value and converts it to int64 without first bounding the result. Any application that passes attacker-controlled range parameters to this operation can abort its TensorFlow process, interrupting only that process.
Summary
What happened
Integer overflow in Google TensorFlow before 2.7.2, 2.8.0, and 2.9.0 allows remote attackers to crash the process via limits. RaggedRangeOp computes ceil(abs((limit - start) / delta)) as a floating-point value and converts it to int64 without first bounding the result. Any application that passes attacker-controlled range parameters to this operation can abort its TensorFlow process, interrupting only that process.
The record
- CVE
- CVE-2022-35940
- Published
- Sep 16, 2022
- Updated
- Apr 23, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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.7.2
- Affected versionversion=>= 2.8.0, < 2.8.1
- Affected versionversion=>= 2.9.0, < 2.9.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
- RaggedRange crash 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