CVE-2022-21732 json
Memory exhaustion in Tensorflow
published 4y ago modified last mo. also BIT-tensorflow-2022-21732 , EUVD-2022-0295 , GHSA-c582-c96p-r5cq , PYSEC-2022-111 , PYSEC-2022-56 , PYSEC-2026-3158
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
Tensorflow is an Open Source Machine Learning Framework. The implementation of `ThreadPoolHandle` can be used to trigger a denial of service attack by allocating too much memory. This is because the `num_threads` argument is only checked to not be negative, but there is no upper bound on its value. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
Patch / fix
- pypi tensorflow 2.5.3, 2.6.3, 2.7.1
- pypi tensorflow-cpu 2.5.3, 2.6.3, 2.7.1
- pypi tensorflow-gpu 2.5.3, 2.6.3, 2.7.1
- bitnami tensorflow 2.5.3, 2.6.3, 2.7.1
Is CVE-2022-21732 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/data/experimental/threadpool_dataset_op.cc#L79-L135 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | <2.5.3 >=2.6.0, <2.6.3 >=2.7.0, <2.7.1 |
2.5.3 2.6.3 2.7.1 |
| pypi | tensorflow-cpu | <2.5.3 >=2.6.0, <2.6.3 >=2.7.0, <2.7.1 |
2.5.3 2.6.3 2.7.1 |
| pypi | tensorflow-gpu | <2.5.3 >=2.6.0, <2.6.3 >=2.7.0, <2.7.1 |
2.5.3 2.6.3 2.7.1 |
| bitnami | tensorflow | <2.5.3 >=2.6.0, <2.6.3 >=2.7.0, <2.7.1 |
2.5.3 2.6.3 2.7.1 |
Classification
References
-
github.com
/tensorflow/tensorflow/commit/e3749a6d5d1e8d11806d4a2e9cc3123d1a90b75e
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-c582-c96p-r5cq
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/data/experimental
web, exploit, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-21732
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-56.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-111.yaml
web
-
github.com
/tensorflow/tensorflow
web
-
pypi.org
/project/tensorflow
package
-
github.com
/advisories/GHSA-c582-c96p-r5cq
advisory
Sources
- CVE List CVE-2022-21732
- GitHub Advisory GHSA-c582-c96p-r5cq
- NVD CVE-2022-21732
- OSV BIT-tensorflow-2022-21732
- OSV PYSEC-2022-111
- OSV PYSEC-2022-56
- OSV PYSEC-2026-3158
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.