CVE-2022-29210
Summary
| CVE | CVE-2022-29210 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-05-21 00:15:00 UTC |
| Updated | 2023-06-28 20:26:00 UTC |
| Description | 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. |
Risk And Classification
Problem Types: CWE-787
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Tensorflow | 2.8.0 | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Release TensorFlow 2.8.1 · tensorflow/tensorflow · GitHub | MISC | github.com | |
| Release TensorFlow 2.9.0 · tensorflow/tensorflow · GitHub | MISC | github.com | |
| Heap buffer overflow due to incorrect hash function · Advisory · tensorflow/tensorflow · GitHub | CONFIRM | github.com | |
| tensorflow/tensor_key.h at f3b9bf4c3c0597563b289c0512e98d4ce81f886e · tensorflow/tensorflow · GitHub | MISC | github.com | |
| Fix TensorKey hash function. · tensorflow/tensorflow@1b85a28 · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.