Process crash via invalid-rank RaggedCross input
Published Nov 5, 2021 · Updated Aug 4, 2024
Denial of service in TensorFlow 2.6.0, 2.5.0 through 2.5.1, and 2.4.3 and earlier allows local users to crash the calling process. RaggedCross shape inference fails to validate that dense inputs have rank two before accessing dimension zero, binding a reference to nullptr for invalid-rank input. The attacker must be able to supply tensors to code that traces the operation; exploitation terminates that process without reported data access or modification.
Summary
What happened
Denial of service in TensorFlow 2.6.0, 2.5.0 through 2.5.1, and 2.4.3 and earlier allows local users to crash the calling process. RaggedCross shape inference fails to validate that dense inputs have rank two before accessing dimension zero, binding a reference to nullptr for invalid-rank input. The attacker must be able to supply tensors to code that traces the operation; exploitation terminates that process without reported data access or modification.
The record
- CVE
- CVE-2021-41214
- Published
- Nov 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-824, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 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.4.4
- Affected versionversion=>= 2.5.0, < 2.5.2
- Affected versionversion=>= 2.6.0, < 2.6.1
What conditions does exploitation require?
What is affected?
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.cross process-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