Code execution via unchecked fractional pooling ratio
Published Nov 18, 2022 · Updated Apr 22, 2025
Heap out-of-bounds access in Google TensorFlow before 2.8.4, 2.9.0 through 2.9.2, and 2.10.0 allows attackers to crash or execute code. The FractionalMaxPool and FractionalAvgPool kernels accept pooling_ratio values below 1 and use them in shape and pooling calculations without first rejecting the illegal ratio, causing access beyond allocated heap buffers. Exploitation requires an application to execute one of these operations with an attacker-influenced pooling ratio; the resulting memory fault can terminate that process or permit code execution.
Summary
What happened
Heap out-of-bounds access in Google TensorFlow before 2.8.4, 2.9.0 through 2.9.2, and 2.10.0 allows attackers to crash or execute code. The FractionalMaxPool and FractionalAvgPool kernels accept pooling_ratio values below 1 and use them in shape and pooling calculations without first rejecting the illegal ratio, causing access beyond allocated heap buffers. Exploitation requires an application to execute one of these operations with an attacker-influenced pooling ratio; the resulting memory fault can terminate that process or permit code execution.
The record
- CVE
- CVE-2022-41900
- Published
- Nov 18, 2022
- Updated
- Apr 22, 2025
- Vendor
- Product
- TensorFlow
- Classifications
- CWE-787, CWE-125, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 18, 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.10.0, < 2.10.1
- Affected versionversion=< 2.8.4
- Affected versionversion=>= 2.9.0, < 2.9.3
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
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