CVE-2021-29570

CVSS V2 Low 3.6 CVSS V3 High 7.1
Description
TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation(https://github.com/tensorflow/tensorflow/blob/ef0c008ee84bad91ec6725ddc42091e19a30cf0e/tensorflow/core/kernels/maxpooling_op.cc#L1016-L1017) uses the same value to index in two different arrays but there is no guarantee that the sizes are identical. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
Overview
  • CVE ID
  • CVE-2021-29570
  • Assigner
  • security-advisories@github.com
  • Vulnerability Status
  • Analyzed
  • Published Version
  • 2021-05-14T20:15:13
  • Last Modified Date
  • 2021-05-18T19:32:07
CPE Configuration (Product)
CPE Vulnerable Operator Version Start Version End
cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:* 1 OR 2.1.4
cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:* 1 OR 2.2.0 2.2.3
cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:* 1 OR 2.3.0 2.3.3
cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:* 1 OR 2.4.0 2.4.2
CVSS Version 2
  • Version
  • 2.0
  • Vector String
  • AV:L/AC:L/Au:N/C:P/I:N/A:P
  • Access Vector
  • LOCAL
  • Access Compatibility
  • LOW
  • Authentication
  • NONE
  • Confidentiality Impact
  • PARTIAL
  • Integrity Impact
  • NONE
  • Availability Impact
  • PARTIAL
  • Base Score
  • 3.6
  • Severity
  • LOW
  • Exploitability Score
  • 3.9
  • Impact Score
  • 4.9
CVSS Version 3
  • Version
  • 3.1
  • Vector String
  • CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
  • Attack Vector
  • LOCAL
  • Attack Compatibility
  • LOW
  • Privileges Required
  • LOW
  • User Interaction
  • NONE
  • Scope
  • UNCHANGED
  • Confidentiality Impact
  • HIGH
  • Availability Impact
  • HIGH
  • Base Score
  • 7.1
  • Base Severity
  • HIGH
  • Exploitability Score
  • 1.8
  • Impact Score
  • 5.2
History
Created Old Value New Value Data Type Notes
2022-05-10 16:15:43 Added to TrackCVE
2022-12-05 02:23:47 2021-05-14T20:15Z 2021-05-14T20:15:13 CVE Published Date updated
2022-12-05 02:23:47 2021-05-18T19:32:07 CVE Modified Date updated
2022-12-05 02:23:47 Analyzed Vulnerability Status updated