First published: Fri May 20 2022(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
TensorFlow Keras | =2.8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-29210 is categorized with a high severity due to its potential impact on machine learning applications using TensorFlow.
To address CVE-2022-29210, update TensorFlow to version 2.8.1 or later, where the vulnerability has been patched.
CVE-2022-29210 specifically affects TensorFlow version 2.8.0.
The implications of CVE-2022-29210 include potential vulnerabilities in tensor management that could lead to inefficient performance or data integrity issues.
Yes, CVE-2022-29210 is directly related to the `TensorKey` hash function used in handling tensor objects in TensorFlow.