Process crash via unchecked ragged rank
Published May 20, 2022 · Updated Apr 22, 2025
Uncontrolled resource consumption in Google TensorFlow allows local users to crash the process through tf.ragged.constant. The _constant_value helper accepts a ragged_rank larger than the input list's maximum depth and uses it to construct nested structure until memory is exhausted. A local low-privileged user who can run TensorFlow code can terminate the hosting Python process or notebook; no confidentiality or integrity impact is reported.
Summary
What happened
Uncontrolled resource consumption in Google TensorFlow allows local users to crash the process through tf.ragged.constant. The _constant_value helper accepts a ragged_rank larger than the input list's maximum depth and uses it to construct nested structure until memory is exhausted. A local low-privileged user who can run TensorFlow code can terminate the hosting Python process or notebook; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2022-29202
- Published
- May 20, 2022
- Updated
- Apr 22, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-400, CWE-20, CWE-1284, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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.6.4
- Affected versionversion=>= 2.7.0rc0, < 2.7.2
- Affected versionversion=>= 2.8.0rc0, < 2.8.1
- Affected versionversion=>= 2.9.0rc0, < 2.9.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
- tf.ragged.constant memory-exhaustion 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