Type confusion leading to segfault in Tensorflow
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-843 and the CVSS impact.
Summary
Tensorflow is an Open Source Machine Learning Framework. The implementation of shape inference for `ConcatV2` can be used to trigger a denial of service attack via a segfault caused by a type confusion. The `axis` argument is translated into `concat_dim` in the `ConcatShapeHelper` helper function. Then, a value for `min_rank` is computed based on `concat_dim`. This is then used to validate that the `values` tensor has at least the required rank. However, `WithRankAtLeast` receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that `min_rank` is a 32-bits value and the value of `axis`, the `rank` argument is a negative value, so the error check is bypassed. 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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
| — | tensorflow (PyPI) | before 2.5.3 | 2.5.3 | Patch available | GHSA-m4hf-j54p-p353 |
| — | tensorflow (PyPI) | 2.6.0 to before 2.6.3 | 2.6.3 | Patch available | GHSA-m4hf-j54p-p353 |
| — | tensorflow (PyPI) | 2.7.0 to before 2.7.1 | 2.7.1 | Patch available | GHSA-m4hf-j54p-p353 |
| — | tensorflow-cpu (PyPI) | before 2.5.3 | 2.5.3 | Patch available | GHSA-m4hf-j54p-p353 |
| — | tensorflow-cpu (PyPI) | 2.6.0 to before 2.6.3 | 2.6.3 | Patch available | GHSA-m4hf-j54p-p353 |
| — | tensorflow-cpu (PyPI) | 2.7.0 to before 2.7.1 | 2.7.1 | Patch available | GHSA-m4hf-j54p-p353 |
| — | tensorflow-gpu (PyPI) | before 2.5.3 | 2.5.3 | Patch available | GHSA-m4hf-j54p-p353 |
| — | tensorflow-gpu (PyPI) | 2.6.0 to before 2.6.3 | 2.6.3 | Patch available | GHSA-m4hf-j54p-p353 |
| — | tensorflow-gpu (PyPI) | 2.7.0 to before 2.7.1 | 2.7.1 | Patch available | GHSA-m4hf-j54p-p353 |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
- tensorflow (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-m4hf-j54p-p353
- tensorflow (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-m4hf-j54p-p353
- tensorflow (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-m4hf-j54p-p353
- tensorflow-cpu (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-m4hf-j54p-p353
- tensorflow-cpu (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-m4hf-j54p-p353
- tensorflow-cpu (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-m4hf-j54p-p353
- tensorflow-gpu (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-m4hf-j54p-p353
- tensorflow-gpu (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-m4hf-j54p-p353
- tensorflow-gpu (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-m4hf-j54p-p353
Remediation
- Fix · GHSA-m4hf-j54p-p353 tensorflow (PyPI) Fixed in 2.5.3 Advisory →
- Fix · GHSA-m4hf-j54p-p353 tensorflow (PyPI) Fixed in 2.6.3 Advisory →
- Fix · GHSA-m4hf-j54p-p353 tensorflow (PyPI) Fixed in 2.7.1 Advisory →
- Fix · GHSA-m4hf-j54p-p353 tensorflow-cpu (PyPI) Fixed in 2.5.3 Advisory →
- Fix · GHSA-m4hf-j54p-p353 tensorflow-cpu (PyPI) Fixed in 2.6.3 Advisory →
- Fix · GHSA-m4hf-j54p-p353 tensorflow-cpu (PyPI) Fixed in 2.7.1 Advisory →
- Fix · GHSA-m4hf-j54p-p353 tensorflow-gpu (PyPI) Fixed in 2.5.3 Advisory →
- Fix · GHSA-m4hf-j54p-p353 tensorflow-gpu (PyPI) Fixed in 2.6.3 Advisory →
- Fix · GHSA-m4hf-j54p-p353 tensorflow-gpu (PyPI) Fixed in 2.7.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2022-21731
- 2026-10-03 Alias added: GHSA-m4hf-j54p-p353
References
Exploit 2
Patch 2
More Google Tensorflow vulnerabilities
- TI-2022-20241 FractionalMaxPool and FractionalAVGPool heap out-of-bounds acess in Tensorflow CVSS 3.1CRITICAL 9.8
- TI-2022-07640 Integer overflow in Tensorflow CVSS 3.1CRITICAL 9.8
- TI-2022-07627 Out of bounds read and write in Tensorflow CVSS 3.1HIGH 8.8
- TI-2022-07619 Out of bounds write in Tensorflow CVSS 3.1HIGH 8.8
- TI-2022-07613 Read and Write outside of bounds in TFLite CVSS 3.1HIGH 8.8
- TI-2022-07612 Integer overflow in TFLite CVSS 3.1HIGH 8.8
Sources
- CVE-2022-21731 · CVE Program
- CVE-2022-21731 · NVD
- FIRST EPSS
- GHSA-m4hf-j54p-p353 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences