CVE-2022-23571 json
Reachable Assertion in Tensorflow
published 4y ago modified 2mo ago also BIT-tensorflow-2022-23571 , EUVD-2022-0319 , GHSA-j3mj-fhpq-qqjj , PYSEC-2022-135 , PYSEC-2022-80 , PYSEC-2026-3204
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
Tensorflow is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes. 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-23571 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.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| 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 |
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 |
Affected products
- tensorflow tensorflow
Classification
- Weakness
-
- CWE-617 Reachable Assertion
References
-
github.com
/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-j3mj-fhpq-qqjj
web, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-23571
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-80.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-135.yaml
web
-
github.com
/tensorflow/tensorflow
web
-
pypi.org
/project/tensorflow
package
-
github.com
/advisories/GHSA-j3mj-fhpq-qqjj
advisory
Sources
- CVE List CVE-2022-23571
- GitHub Advisory GHSA-j3mj-fhpq-qqjj
- NVD CVE-2022-23571
- OSV BIT-tensorflow-2022-23571
- OSV PYSEC-2022-135
- OSV PYSEC-2022-80
- OSV PYSEC-2026-3204
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.