id: PYSEC-2020-276
details: 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.
affected:
- package:
    name: tensorflow-cpu
    ecosystem: PyPI
    purl: pkg:pypi/tensorflow-cpu
  ranges:
  - type: GIT
    repo: https://github.com/tensorflow/tensorflow
    events:
    - introduced: "0"
    - fixed: 3cbb917b4714766030b28eba9fb41bb97ce9ee02
  - type: ECOSYSTEM
    events:
    - introduced: "0"
    - fixed: 2.3.1
  versions:
  - 1.15.0
  - 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
references:
- type: ADVISORY
  url: https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph
- type: WEB
  url: https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
- type: FIX
  url: https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02
aliases:
- CVE-2020-15196
- GHSA-pg59-2f92-5cph
modified: "2021-12-09T06:34:41.429939Z"
published: "2020-09-25T19:15:00Z"