pysec-2020-276
Vulnerability from pysec
Published
2020-09-25 19:15
Modified
2021-12-09 06:34
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.

Impacted products
Name purl
tensorflow-cpu pkg:pypi/tensorflow-cpu
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "tensorflow-cpu",
            purl: "pkg:pypi/tensorflow-cpu",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "3cbb917b4714766030b28eba9fb41bb97ce9ee02",
                  },
               ],
               repo: "https://github.com/tensorflow/tensorflow",
               type: "GIT",
            },
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.3.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         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",
         ],
      },
   ],
   aliases: [
      "CVE-2020-15196",
      "GHSA-pg59-2f92-5cph",
   ],
   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.",
   id: "PYSEC-2020-276",
   modified: "2021-12-09T06:34:41.429939Z",
   published: "2020-09-25T19:15:00Z",
   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",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.