Description
In Tensorflow version 2.3.0, the `SparseCountSparseOutput` and `RaggedCountSparseOutput` implementations don't validate that the `weights` tensor has the same shape as the data. The check exists for `DenseCountSparseOutput`, where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.
References (3)
Core 3
Core References
Third Party Advisory x_refsource_misc
https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
Patch, Third Party Advisory x_refsource_misc
https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02
Exploit, Third Party Advisory x_refsource_confirm
https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph
Scores
CVSS v3
8.5
EPSS
0.0030
EPSS Percentile
53.5%
Attack Vector
NETWORK
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Details
CWE
CWE-119
CWE-125
CWE-122
Status
published
Products (4)
google/tensorflow
2.3.0
pypi/tensorflow
2.3.0 - 2.3.1PyPI
pypi/tensorflow-cpu
2.3.0 - 2.3.1PyPI
pypi/tensorflow-gpu
2.3.0 - 2.3.1PyPI
Published
Sep 25, 2020
Tracked Since
Feb 18, 2026