CVE-2022-29210 json
Heap buffer overflow due to incorrect hash function in TensorFlow
published 4y ago modified 2mo ago also BIT-tensorflow-2022-29210 , EUVD-2022-4120 , GHSA-hc2f-7r5r-r2hg , PYSEC-2026-1007 , PYSEC-2026-3200 , PYSEC-2026-3339
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
TensorFlow is an open source platform for machine learning. In version 2.8.0, the `TensorKey` hash function used total estimated `AllocatedBytes()`, which (a) is an estimate per tensor, and (b) is a very poor hash function for constants (e.g. `int32_t`). It also tried to access individual tensor bytes through `tensor.data()` of size `AllocatedBytes()`. This led to ASAN failures because the `AllocatedBytes()` is an estimate of total bytes allocated by a tensor, including any pointed-to constructs (e.g. strings), and does not refer to contiguous bytes in the `.data()` buffer. The discoverers could not use this byte vector anyway because types such as `tstring` include pointers, whereas they needed to hash the string values themselves. This issue is patched in Tensorflow versions 2.9.0 and 2.8.1.
Patch / fix
- pypi tensorflow 2.8.1
- pypi tensorflow-cpu 2.8.1
- pypi tensorflow-gpu 2.8.1
- bitnami tensorflow 2.8.1
Is CVE-2022-29210 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.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | >=2.8.0, <2.8.1 |
2.8.1 |
| pypi | tensorflow-cpu | >=2.8.0, <2.8.1 |
2.8.1 |
| pypi | tensorflow-gpu | >=2.8.0, <2.8.1 |
2.8.1 |
| bitnami | tensorflow | >=2.8.0, <2.8.1 |
2.8.1 |
Affected products
- tensorflow tensorflow
Classification
References
-
github.com
/tensorflow/tensorflow/commit/1b85a28d395dc91f4d22b5f9e1e9a22e92ccecd6
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-hc2f-7r5r-r2hg
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/releases/tag/v2.8.1
web, release-notes, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/releases/tag/v2.9.0
web, release-notes, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/framework/tensor_key.h#L5
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-29210
advisory, web
-
github.com
/tensorflow/tensorflow
package
-
pypi.org
/project/tensorflow-gpu
package
-
github.com
/advisories/GHSA-hc2f-7r5r-r2hg
advisory
-
pypi.org
/project/tensorflow
package
-
pypi.org
/project/tensorflow-cpu
package
Sources
- CVE List CVE-2022-29210
- GitHub Advisory GHSA-hc2f-7r5r-r2hg
- NVD CVE-2022-29210
- OSV BIT-tensorflow-2022-29210
- OSV PYSEC-2026-1007
- OSV PYSEC-2026-3200
- OSV PYSEC-2026-3339
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.