https://vulnerability.circl.lu/sightings/feed 2026-06-01T20:25:11.765784+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/51fe5c0a-70ec-4274-a8a1-8a48c0916882/export 2026-06-01T20:25:12.208983+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "51fe5c0a-70ec-4274-a8a1-8a48c0916882", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-29210", "type": "seen", "source": "https://t.me/cibsecurity/43138", "content": "\u203c CVE-2022-29210 \u203c\n\nTensorFlow 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.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-05-24T20:49:46.000000Z"} 2022-05-24T20:49:46+00:00