| Summary | 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. |
|---|---|
| Publication Date | Aug. 13, 2021, 8:15 a.m. |
| Registration Date | Aug. 13, 2021, 10 a.m. |
| Last Update | Nov. 21, 2024, 3:15 p.m. |
| CVSS3.1 : MEDIUM | |
| スコア | 5.5 |
|---|---|
| Vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| 攻撃元区分(AV) | ローカル |
| 攻撃条件の複雑さ(AC) | 低 |
| 攻撃に必要な特権レベル(PR) | 低 |
| 利用者の関与(UI) | 不要 |
| 影響の想定範囲(S) | 変更なし |
| 機密性への影響(C) | なし |
| 完全性への影響(I) | なし |
| 可用性への影響(A) | 高 |
| CVSS2.0 : LOW | |
| Score | 2.1 |
|---|---|
| Vector | AV:L/AC:L/Au:N/C:N/I:N/A:P |
| 攻撃元区分(AV) | ローカル |
| 攻撃条件の複雑さ(AC) | 低 |
| 攻撃前の認証要否(Au) | 不要 |
| 機密性への影響(C) | なし |
| 完全性への影響(I) | なし |
| 可用性への影響(A) | 低 |
| Get all privileges. | いいえ |
| Get user privileges | いいえ |
| Get other privileges | いいえ |
| User operation required | いいえ |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:google:tensorflow:*:*:*:*:*:*:*:* | 2.5.0 | 2.6.0 | |||
| Title | TensorFlow における入力確認に関する脆弱性 |
|---|---|
| Summary | TensorFlow には、入力確認に関する脆弱性が存在します。 |
| Possible impacts | サービス運用妨害 (DoS) 状態にされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | July 14, 2021, midnight |
| Registration Date | June 7, 2022, 11:05 a.m. |
| Last Update | June 7, 2022, 11:05 a.m. |
| Google TensorFlow |
| No | Changed Details | Date of change |
|---|---|---|
| 1 | [2022年06月07日] 掲載 |
June 7, 2022, 11:05 a.m. |