Memory exhaustion via unbounded thread-pool allocation
Published Feb 3, 2022 · Updated Feb 12, 2025
Resource exhaustion in TensorFlow 2.5.2 and earlier, 2.6.0 through 2.6.2, and 2.7.0 allows attackers to exhaust memory via ThreadPoolHandle. The operator accepts an attacker-controlled num_threads value without an upper bound and attempts a correspondingly large thread-pool allocation. Reachability requires the ability to make a TensorFlow process execute a raw operation with attacker-controlled attributes; the vendor does not specify whether exhaustion causes a hang or crash.
Summary
What happened
Resource exhaustion in TensorFlow 2.5.2 and earlier, 2.6.0 through 2.6.2, and 2.7.0 allows attackers to exhaust memory via ThreadPoolHandle. The operator accepts an attacker-controlled num_threads value without an upper bound and attempts a correspondingly large thread-pool allocation. Reachability requires the ability to make a TensorFlow process execute a raw operation with attacker-controlled attributes; the vendor does not specify whether exhaustion causes a hang or crash.
The record
- CVE
- CVE-2022-21732
- Published
- Feb 3, 2022
- Updated
- Feb 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 2022CVE publishedPublication date reported by the CVE source.
- Feb 12, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- ThreadPoolHandle oversized-thread-count proof of conceptproof 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