Process crash via empty MLIR function attributes
Published Sep 16, 2022 · Updated Apr 23, 2025
Null pointer dereference in Google TensorFlow before 2.7.2, 2.8.0, and 2.9.0 allows remote attackers to crash processing via malformed MLIR. The mlir::tfg::ConvertGenericFunctionToFunctionDef path dereferences a null value instead of rejecting empty function attributes. An attacker must supply MLIR content that reaches this conversion path; the bounded consequence is process termination and service interruption.
Summary
What happened
Null pointer dereference in Google TensorFlow before 2.7.2, 2.8.0, and 2.9.0 allows remote attackers to crash processing via malformed MLIR. The mlir::tfg::ConvertGenericFunctionToFunctionDef path dereferences a null value instead of rejecting empty function attributes. An attacker must supply MLIR content that reaches this conversion path; the bounded consequence is process termination and service interruption.
The record
- CVE
- CVE-2022-36000
- Published
- Sep 16, 2022
- Updated
- Apr 23, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-476, T1499
- 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.
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