PYSEC-2020-311
See a problem?- Import Source
- https://github.com/pypa/advisory-database/blob/main/vulns/tensorflow-gpu/PYSEC-2020-311.yaml
- JSON Data
- https://api.test.osv.dev/v1/vulns/PYSEC-2020-311
- Aliases
- Published
- 2020-09-25T19:15:00Z
- Modified
- 2023-12-06T00:45:15.481928Z
- Summary
- [none]
- Details
-
In Tensorflow version 2.3.0, the
SparseCountSparseOutputandRaggedCountSparseOutputimplementations don't validate that theweightstensor has the same shape as the data. The check exists forDenseCountSparseOutput, 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
Affected packages
PyPI / tensorflow-gpu
Package
- Name
- tensorflow-gpu
- View open source insights on deps.dev
- Purl
- pkg:pypi/tensorflow-gpu
Affected ranges
- Type
- GIT
- Repo
- https://github.com/tensorflow/tensorflow
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Type
- ECOSYSTEM
- Events
-
Introduced0Unknown introduced version / All previous versions are affectedFixed2.3.1
Affected versions
0.*
0.12.0
0.12.1
1.*
1.0.0
1.0.1
1.1.0
1.2.0
1.2.1
1.3.0
1.4.0
1.4.1
1.5.0
1.5.1
1.6.0
1.7.0
1.7.1
1.8.0
1.9.0
1.10.0
1.10.1
1.11.0
1.12.0
1.12.2
1.12.3
1.13.1
1.13.2
1.14.0
1.15.0
1.15.2
1.15.3
1.15.4
1.15.5
2.*
2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.1.0
2.1.1
2.1.2
2.1.3
2.1.4
2.2.0
2.2.1
2.2.2
2.2.3
2.3.0