7 matches found
CVE-2022-29210
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. int32t. It also tried to access individual tensor bytes through...
acuity (=6.18.0), acuitypro (=6.18.0) +60 more potentially affected by CVE-2022-29210 via tensorflow (>=2.8.0 <=2.8.0rc1)
tensorflow PYPI version =2.8.0, =1.2.8, =1.0.43, =0.2.2, =0.0.1, =0.0.2, =0.2.8, =0.14.0, =0.1.3, =0.0.9, =0.2.27, =0.2.41 - complaintclassify =0.0.5 - conversational-sentence-encoder =0.0.6 and more Source cves: CVE-2022-29210 Source advisory: OSV:GHSA-HC2F-7R5R-R2HG...
causalegm (>=0.2.1 <=0.2.5), chrombpnet (>=0.1.0 <=0.1.2) +3 more potentially affected by CVE-2022-29210 via tensorflow-gpu (=2.8.0)
tensorflow-gpu PYPI version =2.8.0 is affected by a known vulnerability. The following packages have a transitive dependency on tensorflow-gpu and may be impacted: - causalegm =0.2.1, =0.1.0, =0.0.6, =2.3.5, =2.4.1 - tlaunch =0.0.2 Source cves: CVE-2022-29210 Source advisory: OSV:GHSA-HC2F-7R5R-R...
CVE-2022-29210
creationtimestamp| type| source ---|---|--- 2022-05-24 20:49:46+00:00| seen| https://t.me/cibsecurity/43138...
CVE-2022-29210
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. int32t. It also tried to access individual tensor bytes through...
CVE-2022-29210
CVE-2022-29210 affects TensorFlow 2.8.0, where TensorKey's hash using AllocatedBytes() and tensor.data() can cause a heap-buffer/ASAN-related issue leading to a denial of service. The issue is patched in TensorFlow 2.9.0 and also back-ported to 2.8.1. IBM Watson Discovery bulletin and OSV entries...
CVE-2022-29210 Heap buffer overflow due to incorrect hash function in TensorFlow
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. int32t. It also tried to access individual tensor bytes through...