Process crash via non-scalar writer arguments
Published Nov 5, 2021 · Updated Nov 13, 2024
Reachable assertion in Google TensorFlow before 2.4.4, 2.5.0 through 2.5.1, and 2.6.0 allows local users to crash the process. CreateSummaryFileWriterOp reads logdir, max_queue, flush_millis, and filename_suffix tensors as scalars without first verifying that each tensor has exactly one element. A local user must influence an argument passed by the hosting application; a non-scalar value triggers a fatal CHECK and aborts that process.
Summary
What happened
Reachable assertion in Google TensorFlow before 2.4.4, 2.5.0 through 2.5.1, and 2.6.0 allows local users to crash the process. CreateSummaryFileWriterOp reads logdir, max_queue, flush_millis, and filename_suffix tensors as scalars without first verifying that each tensor has exactly one element. A local user must influence an argument passed by the hosting application; a non-scalar value triggers a fatal CHECK and aborts that process.
The record
- CVE
- CVE-2021-41200
- Published
- Nov 5, 2021
- Updated
- Nov 13, 2024
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 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.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?
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.summary.create_file_writer 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