pysec-2020-288
Vulnerability from pysec
Published
2020-09-25 19:15
Modified
2021-12-09 06:34
Details

In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a DCHECK which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue is patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 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: "8ee24e7949a203d234489f9da2c5bf45a7d5157d",
                  },
               ],
               repo: "https://github.com/tensorflow/tensorflow",
               type: "GIT",
            },
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "1.15.4",
                  },
                  {
                     introduced: "2.0.0",
                  },
                  {
                     fixed: "2.0.3",
                  },
                  {
                     introduced: "2.1.0",
                  },
                  {
                     fixed: "2.1.2",
                  },
                  {
                     introduced: "2.2.0",
                  },
                  {
                     fixed: "2.2.1",
                  },
                  {
                     introduced: "2.3.0",
                  },
                  {
                     fixed: "2.3.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "1.15.0",
            "2.1.0",
            "2.1.1",
            "2.2.0",
            "2.3.0",
         ],
      },
   ],
   aliases: [
      "CVE-2020-15208",
      "GHSA-mxjj-953w-2c2v",
   ],
   details: "In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue is patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.",
   id: "PYSEC-2020-288",
   modified: "2021-12-09T06:34:43.041754Z",
   published: "2020-09-25T19:15:00Z",
   references: [
      {
         type: "FIX",
         url: "https://github.com/tensorflow/tensorflow/commit/8ee24e7949a203d234489f9da2c5bf45a7d5157d",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mxjj-953w-2c2v",
      },
      {
         type: "WEB",
         url: "https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html",
      },
   ],
}


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.