CVE-2021-37692

TensorFlow is an end-to-end open source platform for machine learning. In affected versions under certain conditions, Go code can trigger a segfault in string deallocation. For string tensors, `C.TF_TString_Dealloc` is called during garbage collection within a finalizer function. However, tensor structure isn't checked until encoding to avoid a performance penalty. The current method for dealloc assumes that encoding succeeded, but segfaults when a string tensor is garbage collected whose encoding failed (e.g., due to mismatched dimensions). To fix this, the call to set the finalizer function is deferred until `NewTensor` returns and, if encoding failed for a string tensor, deallocs are determined based on bytes written. We have patched the issue in GitHub commit 8721ba96e5760c229217b594f6d2ba332beedf22. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, which is the other affected version.

• CVE ID
• CVE-2021-37692

• Assigner
• security-advisories@github.com

• Vulnerability Status
• Analyzed

• Published Version
• 2021-08-12T23:15:08

• Last Modified Date
• 2021-08-31T16:23:53

• Version
• 2.0

• Vector String
• AV:L/AC:L/Au:N/C:N/I:N/A:P

• Access Vector
• LOCAL

• Access Compatibility
• LOW

• Authentication
• NONE

• Confidentiality Impact
• NONE

• Integrity Impact
• NONE

• Availability Impact
• PARTIAL

• Base Score
• 2.1

• Severity
• LOW

• Exploitability Score
• 3.9

• Impact Score
• 2.9

• Version
• 3.1

• Vector String
• CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

• Attack Vector
• LOCAL

• Attack Compatibility
• LOW

• Privileges Required
• LOW

• User Interaction
• NONE

• Scope
• UNCHANGED

• Confidentiality Impact
• NONE

• Availability Impact
• HIGH

• Base Score
• 5.5

• Base Severity
• MEDIUM

• Exploitability Score
• 1.8

• Impact Score
• 3.6