ID CVE-2021-41213
Summary TensorFlow is an open source platform for machine learning. In affected versions the code behind `tf.function` API can be made to deadlock when two `tf.function` decorated Python functions are mutually recursive. This occurs due to using a non-reentrant `Lock` Python object. Loading any model which contains mutually recursive functions is vulnerable. An attacker can cause denial of service by causing users to load such models and calling a recursive `tf.function`, although this is not a frequent scenario. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
References
Vulnerable Configurations
  • cpe:2.3:a:google:tensorflow:2.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.6.0:-:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.6.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.6.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.6.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.6.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.6.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.6.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.5.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.5.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.5.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.5.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.5.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.5.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.5.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.5.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.7.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.7.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.7.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:-:*:*:-:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:-:*:*:-:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc0:*:*:-:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc0:*:*:-:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc0:*:*:lite:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc0:*:*:lite:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc1:*:*:-:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc1:*:*:-:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc1:*:*:lite:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc1:*:*:lite:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc2:*:*:-:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc2:*:*:-:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc2:*:*:lite:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc2:*:*:lite:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc3:*:*:-:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc3:*:*:-:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc3:*:*:lite:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc3:*:*:lite:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.0:rc4:*:*:-:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.0:rc4:*:*:-:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:google:tensorflow:2.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:google:tensorflow:2.4.3:*:*:*:*:*:*:*
CVSS
Base: 4.3 (as of 20-10-2022 - 21:25)
Impact:
Exploitability:
CWE CWE-662
CAPEC
  • Leveraging Race Conditions via Symbolic Links
    This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to her. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file she will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.
  • Forced Deadlock
    The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing actions are waiting for each other to finish, and thus neither ever does. Deadlock conditions can be difficult to detect.
  • Leveraging Race Conditions
    The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with his version and cause the system to read the malicious file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
    This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
NONE NONE PARTIAL
cvss-vector via4 AV:N/AC:M/Au:N/C:N/I:N/A:P
Last major update 20-10-2022 - 21:25
Published 05-11-2021 - 23:15
Last modified 20-10-2022 - 21:25
Back to Top