pysec-2019-227
Vulnerability from pysec
Published
2019-12-16 21:15
Modified
2021-08-27 03:22
Details

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.

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: "db4f9717c41bccc3ce10099ab61996b246099892",
                  },
               ],
               repo: "https://github.com/tensorflow/tensorflow",
               type: "GIT",
            },
            {
               events: [
                  {
                     introduced: "1.0.0",
                  },
                  {
                     fixed: "1.15.0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2019-16778",
      "GHSA-844w-j86r-4x2j",
   ],
   details: "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.",
   id: "PYSEC-2019-227",
   modified: "2021-08-27T03:22:22.453759Z",
   published: "2019-12-16T21:15:00Z",
   references: [
      {
         type: "FIX",
         url: "https://github.com/tensorflow/tensorflow/commit/db4f9717c41bccc3ce10099ab61996b246099892",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2019-002.md",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/tensorflow/tensorflow/security/advisories/GHSA-844w-j86r-4x2j",
      },
   ],
}


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.