CVE-2019-16778
published 2019-12-16CVE-2019-16778: In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and…
critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | tensorflow | — | — |
| tensorflow | >= 1.0.0 < 1.15.0 | 1.15.0 | |
| intel | optimization_for_tensorflow | >= 0 < 1.15.0 | 1.15.0 |
| intel | optimization_for_tensorflow | >= 0 < db4f9717c41bccc3ce10099ab61996b246099892 | db4f9717c41bccc3ce10099ab61996b246099892 |
| intel | optimization_for_tensorflow | >= 1.0.0 < 1.15.0 | 1.15.0 |
| tensorflow | tensorflow | < 1.15 | 1.15 |
Debian
CVE-2019-16778: tensorflow - In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be p...
vendor_debian·2019·CVSS 2.6
CVE-2019-16778 [LOW] CVE-2019-16778: tensorflow - In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be p...
In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.
Scope: local
forky: resolved
sid: resolved
OSV
Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
osv·2019-12-16
CVE-2019-16778 [LOW] Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
### Impact
A heap buffer overflow in `UnsortedSegmentSum` can be produced when the `Index` template argument is `int32`. In this case `data_size` and `num_segments` fields are truncated from `int64` to `int32` and can produce negative numbers, resulting in accessing out of bounds heap memory.
This is unlikely to be exploitable and was detected and fixed internally. We are making the security advisory only to notify users that it is better to update to TensorFlow 1.15 or 2.0 or later as these versions already have this fixed.
### Patches
Patched by db4f9717c41bccc3ce10099ab61996b246099892 and released in all official releases after 1.15 and 2.0.
### For more information
Please consult [`SECURITY.md`](https://github.com/tensorf
GHSA
Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
ghsa·2019-12-16
CVE-2019-16778 [LOW] CWE-122 Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
Heap buffer overflow in `UnsortedSegmentSum` in TensorFlow
### Impact
A heap buffer overflow in `UnsortedSegmentSum` can be produced when the `Index` template argument is `int32`. In this case `data_size` and `num_segments` fields are truncated from `int64` to `int32` and can produce negative numbers, resulting in accessing out of bounds heap memory.
This is unlikely to be exploitable and was detected and fixed internally. We are making the security advisory only to notify users that it is better to update to TensorFlow 1.15 or 2.0 or later as these versions already have this fixed.
### Patches
Patched by db4f9717c41bccc3ce10099ab61996b246099892 and released in all official releases after 1.15 and 2.0.
### For more information
Please consult [`SECURITY.md`](https://github.com/tensorf
OSV
CVE-2019-16778: In TensorFlow before 1
osv·2019-12-16
CVE-2019-16778 CVE-2019-16778: In TensorFlow before 1
In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2019-002.mdhttps://github.com/tensorflow/tensorflow/commit/db4f9717c41bccc3ce10099ab61996b246099892https://github.com/tensorflow/tensorflow/security/advisories/GHSA-844w-j86r-4x2jhttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2019-002.mdhttps://github.com/tensorflow/tensorflow/commit/db4f9717c41bccc3ce10099ab61996b246099892https://github.com/tensorflow/tensorflow/security/advisories/GHSA-844w-j86r-4x2j
2019-12-16
Published