Version 2.12.0
tensorflow-gpu
Removed: please install "tensorflow" instead.
Install Instructions
pip install tensorflow-gpu
Current Version Release Date January 24, 2023
Language Python
Package URL (purl) pkg:pip/tensorflow-gpu@2.12.0
Find tensorflow-gpu vulnerabilities in your supply chain.
tensorflow-gpu Vulnerabilities
Sort by
CVE (Latest)
CVE (Latest)
-
CVE (Latest)
-
CVE (Oldest)
-
CVSS Score (Highest)
-
CVSS Score (Lowest)
CVE  |
CVSS Score |
CWE(s) |
EPSS Score |
EPSS % |
Impacted Versions |
|---|---|---|---|---|---|
| CVE-2018-10055 | High 8.1 | CWE-119 | 0.00127 | 0.48735 |
|
| CVE-2018-21233 | Medium 6.5 | CWE-125 | 0.00085 | 0.37661 |
|
| CVE-2018-7575 | High 9.8 | CWE-190 | 0.00119 | 0.47468 |
|
| CVE-2018-7576 | Medium 6.5 | CWE-476 | 0.00086 | 0.37881 |
|
| CVE-2018-7577 | High 8.1 | CWE-20 | 0.00112 | 0.46084 |
|
| CVE-2019-16778 | High 9.8 | CWE-681 | 0.00168 | 0.54655 |
|
| CVE-2019-9635 | Medium 6.5 | CWE-476 | 0.00086 | 0.37881 |
|
| CVE-2020-15190 | Medium 5.3 | CWE-20, CWE-476 | 0.00233 | 0.62027 |
|
| CVE-2020-15191 | Medium 5.3 | CWE-20, CWE-252, CWE-476 | 0.00233 | 0.62027 |
|
| CVE-2020-15192 | Medium 4.3 | CWE-20 | 0.00201 | 0.58668 |
|
| CVE-2020-15193 | High 7.1 | CWE-908 | 0.00151 | 0.52458 |
|
| CVE-2020-15194 | Medium 5.3 | CWE-20, CWE-617 | 0.00196 | 0.58202 |
|
| CVE-2020-15195 | High 8.8 | CWE-119, CWE-122, CWE-787 | 0.00455 | 0.75914 |
|
| CVE-2020-15196 | High 9.9 | CWE-119, CWE-125, CWE-122 | 0.00246 | 0.65305 |
|
| CVE-2020-15197 | Medium 6.3 | CWE-20, CWE-617 | 0.00182 | 0.56585 |
|
| CVE-2020-15198 | Medium 5.4 | CWE-119, CWE-122 | 0.00096 | 0.41693 |
|
| CVE-2020-15199 | Medium 5.9 | CWE-20 | 0.00218 | 0.60533 |
|
| CVE-2020-15200 | Medium 5.9 | CWE-20, CWE-122, CWE-787 | 0.00295 | 0.69964 |
|
| CVE-2020-15201 | Medium 4.8 | CWE-20, CWE-122, CWE-787 | 0.00127 | 0.4878 |
|
| CVE-2020-15202 | High 9 | CWE-754, CWE-197 | 0.00267 | 0.6836 |
|
| CVE-2020-15204 | Medium 5.3 | CWE-476 | 0.00145 | 0.51612 |
|
| CVE-2020-15205 | High 9.8 | CWE-119, CWE-122, CWE-787 | 0.00209 | 0.59532 |
|
| CVE-2020-15203 | High 7.5 | CWE-134, CWE-20 | 0.00259 | 0.66263 |
|
| CVE-2020-15206 | High 7.5 | CWE-20 | 0.00271 | 0.68615 |
|
| CVE-2020-15207 | High 9 | CWE-119, CWE-787 | 0.00273 | 0.68685 |
|
| CVE-2020-15208 | High 9.8 | CWE-125, CWE-787 | 0.00166 | 0.54428 |
|
| CVE-2020-15209 | Medium 5.9 | CWE-476 | 0.00157 | 0.53203 |
|
| CVE-2020-15210 | Medium 6.5 | CWE-787 | 0.00199 | 0.58567 |
|
| CVE-2020-15211 | Medium 4.8 | CWE-125, CWE-787 | 0.00241 | 0.64848 |
|
| CVE-2020-15265 | High 7.5 | CWE-125 | 0.00192 | 0.57885 |
|
| CVE-2020-15266 | High 7.5 | CWE-119 | 0.00172 | 0.55228 |
|
| CVE-2020-26266 | Medium 5.3 | CWE-908 | 0.0009 | 0.3971 |
|
| CVE-2020-26267 | High 7.8 | CWE-125 | 0.00048 | 0.19481 |
|
| CVE-2020-26268 | Medium 4.4 | CWE-471 | 0.00044 | 0.14248 |
|
| CVE-2020-26270 | Low 3.3 | CWE-20 | 0.00044 | 0.14048 |
|
| CVE-2020-26271 | Low 3.3 | CWE-908, CWE-125 | 0.00044 | 0.14248 |
|
| CVE-2020-5215 | High 7.5 | CWE-754, CWE-20 | 0.00362 | 0.73012 |
|
| CVE-2021-29513 | High 7.8 | CWE-843, CWE-476 | 0.00048 | 0.19481 |
|
| CVE-2021-29515 | High 7.8 | CWE-476 | 0.00048 | 0.19481 |
|
| CVE-2021-29516 | Medium 5.5 | CWE-476 | 0.00044 | 0.14248 |
|
| CVE-2021-29517 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29518 | High 7.8 | CWE-476 | 0.00048 | 0.19481 |
|
| CVE-2021-29519 | Medium 5.5 | CWE-843 | 0.00044 | 0.14248 |
|
| CVE-2021-29520 | High 7.8 | CWE-787, CWE-120 | 0.00048 | 0.19481 |
|
| CVE-2021-29522 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29523 | Medium 5.5 | CWE-190 | 0.00044 | 0.14248 |
|
| CVE-2021-29524 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29525 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29526 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29527 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29528 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29529 | High 7.8 | CWE-193 | 0.00048 | 0.19481 |
|
| CVE-2021-29530 | High 7.8 | CWE-476 | 0.00098 | 0.42151 |
|
| CVE-2021-29531 | Medium 5.5 | CWE-754 | 0.00044 | 0.14248 |
|
| CVE-2021-29532 | High 7.1 | CWE-125 | 0.00048 | 0.19481 |
|
| CVE-2021-29533 | Medium 5.5 | CWE-754 | 0.0009 | 0.3971 |
|
| CVE-2021-29534 | Medium 5.5 | CWE-754 | 0.00044 | 0.14248 |
|
| CVE-2021-29535 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29536 | High 7.8 | CWE-787, CWE-131 | 0.00048 | 0.19481 |
|
| CVE-2021-29537 | High 7.8 | CWE-787, CWE-131 | 0.00048 | 0.19481 |
|
| CVE-2021-29538 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29539 | Medium 5.5 | CWE-681 | 0.00044 | 0.14248 |
|
| CVE-2021-29540 | High 7.8 | CWE-787, CWE-120 | 0.00048 | 0.19481 |
|
| CVE-2021-29541 | Medium 5.5 | CWE-476 | 0.00044 | 0.14248 |
|
| CVE-2021-29542 | Medium 5.5 | CWE-787 | 0.0006 | 0.27125 |
|
| CVE-2021-29543 | Medium 5.5 | CWE-617 | 0.00044 | 0.14248 |
|
| CVE-2021-29545 | Medium 5.5 | CWE-131 | 0.00044 | 0.14248 |
|
| CVE-2021-29546 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29547 | Medium 5.5 | CWE-125 | 0.00044 | 0.14248 |
|
| CVE-2021-29548 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29549 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29550 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29551 | Medium 5.5 | CWE-125 | 0.0009 | 0.3971 |
|
| CVE-2021-29552 | Medium 5.5 | CWE-617 | 0.00044 | 0.14248 |
|
| CVE-2021-29553 | High 7.1 | CWE-125 | 0.00048 | 0.19481 |
|
| CVE-2021-29554 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29555 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29556 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29557 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29558 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29559 | High 7.1 | CWE-125 | 0.00048 | 0.19481 |
|
| CVE-2021-29560 | High 7.1 | CWE-125, CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29561 | Medium 5.5 | CWE-617 | 0.00044 | 0.14248 |
|
| CVE-2021-29562 | Medium 5.5 | CWE-617 | 0.00044 | 0.14248 |
|
| CVE-2021-29563 | Medium 5.5 | CWE-617 | 0.00044 | 0.14248 |
|
| CVE-2021-29564 | Medium 5.5 | CWE-476 | 0.00044 | 0.14248 |
|
| CVE-2021-29565 | Medium 5.5 | CWE-476 | 0.00044 | 0.14248 |
|
| CVE-2021-29566 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29567 | Medium 5.5 | CWE-617 | 0.00044 | 0.14248 |
|
| CVE-2021-29568 | High 7.8 | CWE-824, CWE-476 | 0.00051 | 0.21591 |
|
| CVE-2021-29569 | High 7.1 | CWE-125 | 0.00048 | 0.19481 |
|
| CVE-2021-29570 | High 7.1 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-29571 | High 7.8 | CWE-787 | 0.00098 | 0.42151 |
|
| CVE-2021-29572 | Medium 5.5 | CWE-476 | 0.00044 | 0.14248 |
|
| CVE-2021-29573 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29574 | High 7.8 | CWE-476 | 0.00048 | 0.19481 |
|
| CVE-2021-29575 | Medium 5.5 | CWE-787 | 0.0006 | 0.27125 |
|
| CVE-2021-29576 | High 7.8 | CWE-119, CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29577 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29578 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29579 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29580 | Medium 5.5 | CWE-908 | 0.00044 | 0.14248 |
|
| CVE-2021-29581 | Medium 5.5 | CWE-908 | 0.00044 | 0.14248 |
|
| CVE-2021-29582 | High 7.1 | CWE-125 | 0.00048 | 0.19481 |
|
| CVE-2021-29583 | High 7.8 | CWE-125, CWE-476 | 0.00048 | 0.19481 |
|
| CVE-2021-29584 | Medium 5.5 | CWE-190 | 0.00044 | 0.14248 |
|
| CVE-2021-29585 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29586 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29587 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29588 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29589 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29590 | High 7.1 | CWE-125 | 0.00048 | 0.19481 |
|
| CVE-2021-29591 | High 7.8 | CWE-835, CWE-674 | 0.00092 | 0.40826 |
|
| CVE-2021-29592 | High 7.8 | CWE-476 | 0.00048 | 0.19481 |
|
| CVE-2021-29593 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29594 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29595 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29596 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29597 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29598 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29599 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29600 | High 7.8 | CWE-369 | 0.00048 | 0.19481 |
|
| CVE-2021-29601 | High 7.1 | CWE-190 | 0.00044 | 0.14248 |
|
| CVE-2021-29602 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29603 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29604 | Medium 5.5 | CWE-369 | 0.00044 | 0.14248 |
|
| CVE-2021-29605 | Medium 5.5 | CWE-190 | 0.00044 | 0.14248 |
|
| CVE-2021-29606 | High 7.8 | CWE-125 | 0.00048 | 0.19481 |
|
| CVE-2021-29607 | High 7.8 | CWE-754 | 0.00092 | 0.40826 |
|
| CVE-2021-29608 | High 7.8 | CWE-131 | 0.00081 | 0.36023 |
|
| CVE-2021-29609 | High 7.8 | CWE-787, CWE-476 | 0.00092 | 0.40826 |
|
| CVE-2021-29610 | High 7.8 | CWE-665, CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29612 | High 7.8 | CWE-787 | 0.00113 | 0.46213 |
|
| CVE-2021-29613 | High 7.1 | CWE-665, CWE-125 | 0.00092 | 0.40826 |
|
| CVE-2021-29614 | High 7.8 | CWE-665, CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29615 | Medium 5.5 | CWE-674 | 0.00044 | 0.14248 |
|
| CVE-2021-29616 | High 7.8 | CWE-476 | 0.00048 | 0.19481 |
|
| CVE-2021-29617 | Medium 5.5 | CWE-755 | 0.00086 | 0.38014 |
|
| CVE-2021-29618 | Medium 5.5 | CWE-755 | 0.00086 | 0.38014 |
|
| CVE-2021-29619 | Medium 5.5 | CWE-755 | 0.00044 | 0.14248 |
|
| CVE-2021-37635 | High 7.1 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-37636 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37637 | Medium 5.5 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37638 | High 7.8 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37639 | High 7.8 | CWE-125, CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37640 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37641 | High 7.1 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-37642 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37643 | High 7.1 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37644 | Medium 5.5 | CWE-617 | 0.00044 | 0.14048 |
|
| CVE-2021-37645 | Medium 5.5 | CWE-681 | 0.00044 | 0.14048 |
|
| CVE-2021-37646 | Medium 5.5 | CWE-681 | 0.00044 | 0.14048 |
|
| CVE-2021-37647 | Medium 5.5 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37648 | High 7.8 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37649 | Medium 5.5 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37650 | High 7.8 | CWE-787 | 0.00044 | 0.14048 |
|
| CVE-2021-37651 | High 7.8 | CWE-787 | 0.00044 | 0.14048 |
|
| CVE-2021-37652 | High 7.8 | CWE-415 | 0.00044 | 0.14048 |
|
| CVE-2021-37653 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37654 | High 7.1 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-37655 | High 7.3 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-37656 | High 7.8 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-37657 | High 7.8 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-37658 | High 7.8 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-37659 | High 7.8 | CWE-125, CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37660 | Medium 5.5 | CWE-369 | 0.00042 | 0.05119 |
|
| CVE-2021-37661 | Medium 5.5 | CWE-681 | 0.00044 | 0.14048 |
|
| CVE-2021-37662 | High 7.8 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-37663 | High 7.8 | CWE-20 | 0.00044 | 0.14048 |
|
| CVE-2021-37664 | High 7.1 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-37665 | High 7.8 | CWE-20 | 0.00044 | 0.14048 |
|
| CVE-2021-37666 | High 7.8 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-37667 | High 7.8 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-37668 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37669 | Medium 5.5 | CWE-681 | 0.00044 | 0.14048 |
|
| CVE-2021-37670 | Medium 5.5 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-37671 | High 7.8 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-37672 | Medium 5.5 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-37673 | Medium 5.5 | CWE-20 | 0.00044 | 0.14048 |
|
| CVE-2021-37674 | Medium 5.5 | CWE-1284, CWE-20 | 0.00044 | 0.14048 |
|
| CVE-2021-37675 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37676 | High 7.8 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-37677 | Medium 5.5 | CWE-1284, CWE-20 | 0.00044 | 0.14048 |
|
| CVE-2021-37678 | High 8.8 | CWE-502 | 0.00044 | 0.14048 |
|
| CVE-2021-37679 | High 7.8 | CWE-681 | 0.00044 | 0.14048 |
|
| CVE-2021-37682 | High 7.1 | CWE-908 | 0.00042 | 0.05119 |
|
| CVE-2021-37684 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37685 | Medium 5.5 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-37686 | Medium 5.5 | CWE-835 | 0.00042 | 0.05119 |
|
| CVE-2021-37688 | Medium 5.5 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37689 | Medium 5.5 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37690 | Medium 6.6 | CWE-416 | 0.00042 | 0.05119 |
|
| CVE-2021-37691 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-41195 | Medium 5.5 | CWE-190 | 0.00093 | 0.41035 |
|
| CVE-2021-41196 | Medium 5.5 | CWE-191 | 0.00085 | 0.37459 |
|
| CVE-2021-41197 | Medium 5.5 | CWE-190 | 0.00098 | 0.42242 |
|
| CVE-2021-41198 | Medium 5.5 | CWE-190 | 0.00085 | 0.37459 |
|
| CVE-2021-41199 | Medium 5.5 | CWE-190 | 0.00085 | 0.37459 |
|
| CVE-2021-41200 | Medium 5.5 | CWE-617 | 0.00085 | 0.37459 |
|
| CVE-2021-41201 | High 7.8 | CWE-824 | 0.00048 | 0.19222 |
|
| CVE-2021-41202 | Medium 5.5 | CWE-681 | 0.00045 | 0.15555 |
|
| CVE-2021-41203 | High 7.8 | CWE-190 | 0.00045 | 0.15555 |
|
| CVE-2021-41204 | Medium 5.5 | CWE-824 | 0.00044 | 0.14048 |
|
| CVE-2021-41205 | High 7.1 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-41206 | High 7.8 | CWE-354 | 0.00045 | 0.15555 |
|
| CVE-2021-41207 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-41208 | High 7.8 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-41209 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-41210 | High 7.1 | CWE-125 | 0.00044 | 0.14048 |
|
| CVE-2021-41212 | High 7.1 | CWE-125 | 0.00048 | 0.19222 |
|
| CVE-2021-41213 | Medium 5.5 | CWE-662 | 0.00056 | 0.24603 |
|
| CVE-2021-41214 | High 7.8 | CWE-824 | 0.00048 | 0.19222 |
|
| CVE-2021-41215 | Medium 5.5 | CWE-476 | 0.00044 | 0.14248 |
|
| CVE-2021-41216 | High 7.8 | CWE-787 | 0.00044 | 0.14048 |
|
| CVE-2021-41217 | Medium 5.5 | CWE-476 | 0.00044 | 0.14248 |
|
| CVE-2021-41218 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-41219 | High 7.8 | CWE-125 | 0.00048 | 0.19222 |
|
| CVE-2021-41221 | High 7.8 | CWE-787 | 0.00048 | 0.19222 |
|
| CVE-2021-41222 | Medium 5.5 | CWE-682 | 0.00044 | 0.14248 |
|
| CVE-2021-41223 | High 7.1 | CWE-125 | 0.00048 | 0.19222 |
|
| CVE-2021-41224 | High 7.1 | CWE-125 | 0.00048 | 0.19222 |
|
| CVE-2021-41225 | High 7.8 | CWE-908 | 0.00048 | 0.19222 |
|
| CVE-2021-41226 | High 7.1 | CWE-125 | 0.00048 | 0.19222 |
|
| CVE-2021-41227 | Medium 5.5 | CWE-125 | 0.00066 | 0.30665 |
|
| CVE-2021-41228 | High 7.8 | CWE-94 | 0.00065 | 0.30053 |
|
| CVE-2022-21725 | Medium 6.5 | CWE-369 | 0.00155 | 0.52839 |
|
| CVE-2022-21726 | High 8.8 | CWE-125 | 0.00286 | 0.6949 |
|
| CVE-2022-21727 | High 8.8 | CWE-190 | 0.00361 | 0.72978 |
|
| CVE-2022-21728 | High 8.1 | CWE-125 | 0.00731 | 0.81315 |
|
| CVE-2022-21729 | Medium 6.5 | CWE-190 | 0.00155 | 0.52839 |
|
| CVE-2022-21730 | High 8.1 | CWE-125 | 0.00286 | 0.6949 |
|
| CVE-2022-21731 | Medium 6.5 | CWE-843 | 0.00245 | 0.65216 |
|
| CVE-2022-21732 | Medium 6.5 | CWE-770 | 0.00218 | 0.60536 |
|
| CVE-2022-21733 | Medium 6.5 | CWE-190 | 0.00155 | 0.52839 |
|
| CVE-2022-21734 | Medium 6.5 | CWE-843 | 0.00155 | 0.52839 |
|
| CVE-2022-21735 | Medium 6.5 | CWE-369 | 0.00155 | 0.52839 |
|
| CVE-2022-21736 | Medium 6.5 | CWE-476 | 0.00155 | 0.52839 |
|
| CVE-2022-21737 | Medium 6.5 | CWE-754 | 0.00155 | 0.52839 |
|
| CVE-2022-21738 | Medium 6.5 | CWE-190 | 0.00155 | 0.52839 |
|
| CVE-2022-21739 | Medium 6.5 | CWE-476 | 0.00155 | 0.52839 |
|
| CVE-2022-21740 | High 8.8 | CWE-787 | 0.00693 | 0.80758 |
|
| CVE-2022-21741 | Medium 6.5 | CWE-369 | 0.00155 | 0.52839 |
|
| CVE-2022-23557 | Medium 6.5 | CWE-369 | 0.00155 | 0.52839 |
|
| CVE-2022-23558 | High 8.8 | CWE-190 | 0.01005 | 0.84234 |
|
| CVE-2022-23559 | High 8.8 | CWE-190 | 0.00496 | 0.769 |
|
| CVE-2022-23560 | High 8.8 | CWE-125, CWE-787 | 0.00286 | 0.6949 |
|
| CVE-2022-23561 | High 8.8 | CWE-787 | 0.00104 | 0.43979 |
|
| CVE-2022-23562 | High 8.8 | CWE-190 | 0.00285 | 0.69411 |
|
| CVE-2022-23563 | Medium 6.3 | CWE-668, CWE-367 | 0.00042 | 0.05119 |
|
| CVE-2022-23564 | Medium 6.5 | CWE-617 | 0.00076 | 0.34402 |
|
| CVE-2022-23565 | Medium 6.5 | CWE-617 | 0.00076 | 0.34402 |
|
| CVE-2022-23566 | High 8.8 | CWE-787 | 0.00822 | 0.82488 |
|
| CVE-2022-23567 | Medium 6.5 | CWE-190 | 0.00332 | 0.71847 |
|
| CVE-2022-23568 | Medium 6.5 | CWE-190 | 0.00314 | 0.70963 |
|
| CVE-2022-23569 | Medium 6.5 | CWE-617 | 0.00076 | 0.34402 |
|
| CVE-2022-23570 | Medium 6.5 | CWE-617, CWE-476 | 0.00143 | 0.51396 |
|
| CVE-2022-23571 | Medium 6.5 | CWE-617 | 0.00076 | 0.34402 |
|
| CVE-2022-23572 | Medium 6.5 | CWE-754, CWE-617 | 0.00143 | 0.51396 |
|
| CVE-2022-23573 | High 8.8 | CWE-908 | 0.00288 | 0.6962 |
|
| CVE-2022-23575 | Medium 6.5 | CWE-190 | 0.00155 | 0.52839 |
|
| CVE-2022-23574 | High 8.8 | CWE-125, CWE-787 | 0.00286 | 0.6949 |
|
| CVE-2022-23576 | Medium 6.5 | CWE-190 | 0.00155 | 0.52839 |
|
| CVE-2022-23577 | Medium 6.5 | CWE-476 | 0.00155 | 0.52839 |
|
| CVE-2022-23578 | Medium 4.3 | CWE-401 | 0.00111 | 0.45759 |
|
| CVE-2022-23579 | Medium 6.5 | CWE-617 | 0.00155 | 0.52839 |
|
| CVE-2022-23580 | Medium 6.5 | CWE-1284, CWE-400 | 0.00155 | 0.52839 |
|
| CVE-2022-23581 | Medium 6.5 | CWE-617 | 0.00353 | 0.72687 |
|
| CVE-2022-23582 | Medium 6.5 | CWE-617 | 0.00155 | 0.52839 |
|
| CVE-2022-23583 | Medium 6.5 | CWE-843, CWE-617 | 0.00155 | 0.52839 |
|
| CVE-2022-23584 | Medium 6.5 | CWE-416 | 0.00155 | 0.52839 |
|
| CVE-2022-23585 | Medium 6.5 | CWE-401 | 0.00222 | 0.61204 |
|
| CVE-2022-23586 | Medium 6.5 | CWE-617 | 0.00319 | 0.71211 |
|
| CVE-2022-23587 | High 9.8 | CWE-190 | 0.00358 | 0.72863 |
|
| CVE-2022-23588 | Medium 6.5 | CWE-617 | 0.00245 | 0.65216 |
|
| CVE-2022-23589 | Medium 6.5 | CWE-476 | 0.00369 | 0.7329 |
|
| CVE-2022-23590 | High 7.5 | CWE-754 | 0.00192 | 0.57885 |
|
| CVE-2022-23591 | High 7.5 | CWE-674, CWE-400 | 0.00088 | 0.39048 |
|
| CVE-2022-23595 | Medium 6.5 | CWE-476 | 0.00155 | 0.52839 |
|
| CVE-2022-29191 | Medium 5.5 | CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29192 | Medium 5.5 | CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29193 | Medium 5.5 | CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29194 | Medium 5.5 | CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29195 | Medium 5.5 | CWE-20 | 0.00093 | 0.41035 |
|
| CVE-2022-29196 | Medium 5.5 | CWE-1284, CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29197 | Medium 5.5 | CWE-20 | 0.00093 | 0.41035 |
|
| CVE-2022-29198 | Medium 5.5 | CWE-20 | 0.00093 | 0.41035 |
|
| CVE-2022-29199 | Medium 5.5 | CWE-20 | 0.00093 | 0.41035 |
|
| CVE-2022-29200 | Medium 5.5 | CWE-1284, CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29201 | Medium 5.5 | CWE-20, CWE-476 | 0.00098 | 0.42242 |
|
| CVE-2022-29202 | Medium 5.5 | CWE-1284, CWE-20, CWE-400 | 0.00098 | 0.42242 |
|
| CVE-2022-29203 | Medium 5.5 | CWE-190 | 0.00098 | 0.42242 |
|
| CVE-2022-29204 | Medium 5.5 | CWE-20 | 0.00093 | 0.41035 |
|
| CVE-2022-29205 | Medium 5.5 | CWE-908, CWE-476 | 0.00098 | 0.42242 |
|
| CVE-2022-29206 | Medium 5.5 | CWE-20, CWE-476 | 0.00099 | 0.42355 |
|
| CVE-2022-29207 | Medium 5.5 | CWE-475, CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29208 | High 7.1 | CWE-787 | 0.00093 | 0.41035 |
|
| CVE-2022-29209 | Medium 5.5 | CWE-843 | 0.001 | 0.42741 |
|
| CVE-2022-29211 | Medium 5.5 | CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29212 | Medium 5.5 | CWE-20 | 0.00098 | 0.42242 |
|
| CVE-2022-29213 | Medium 5.5 | CWE-20, CWE-617 | 0.00093 | 0.41035 |
|
| CVE-2022-29216 | High 7.8 | CWE-94 | 0.00095 | 0.4155 |
|
| CVE-2022-35934 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35935 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35937 | High 9.1 | CWE-125 | 0.0014 | 0.5097 |
|
| CVE-2022-35939 | High 9.8 | CWE-787 | 0.00143 | 0.51335 |
|
| CVE-2022-35940 | High 7.5 | CWE-190 | 0.00094 | 0.41325 |
|
| CVE-2022-35941 | High 7.5 | CWE-617 | 0.00094 | 0.41325 |
|
| CVE-2022-35952 | High 7.5 | CWE-617 | 0.00094 | 0.41325 |
|
| CVE-2022-35959 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35960 | High 7.5 | CWE-617 | 0.00094 | 0.41325 |
|
| CVE-2022-35963 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35964 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35965 | High 7.5 | CWE-476 | 0.00082 | 0.36458 |
|
| CVE-2022-35966 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35967 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35968 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35969 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35970 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35971 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35972 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35973 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35974 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35979 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35981 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35982 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-35983 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35984 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35985 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35987 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35988 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35989 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35990 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35991 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35992 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35993 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35994 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35995 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35996 | High 7.5 | CWE-369 | 0.00082 | 0.36458 |
|
| CVE-2022-35997 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-35999 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36000 | High 7.5 | CWE-476 | 0.00082 | 0.36458 |
|
| CVE-2022-36001 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36002 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36003 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36004 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36005 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36011 | High 7.5 | CWE-476 | 0.00082 | 0.36458 |
|
| CVE-2022-36012 | High 7.5 | CWE-617 | 0.00094 | 0.41325 |
|
| CVE-2022-36013 | High 7.5 | CWE-476 | 0.00094 | 0.41325 |
|
| CVE-2022-36014 | High 7.5 | CWE-476 | 0.00152 | 0.5254 |
|
| CVE-2022-36015 | High 7.5 | CWE-190 | 0.00094 | 0.41325 |
|
| CVE-2022-36016 | High 7.5 | CWE-617 | 0.00094 | 0.41325 |
|
| CVE-2022-36017 | High 7.5 | CWE-20 | 0.00075 | 0.33939 |
|
| CVE-2022-36018 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36019 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36026 | High 7.5 | CWE-617 | 0.00082 | 0.36458 |
|
| CVE-2022-36027 | High 7.5 | CWE-20 | 0.00102 | 0.43008 |
|
| CVE-2022-41880 | High 9.1 | CWE-125 | 0.0018 | 0.56315 |
|
| CVE-2022-41884 | High 7.5 | CWE-670 | 0.0008 | 0.35781 |
|
| CVE-2022-41885 | High 7.5 | CWE-131 | 0.00128 | 0.48862 |
|
| CVE-2022-41886 | High 7.5 | CWE-131 | 0.00128 | 0.48862 |
|
| CVE-2022-41887 | High 7.5 | CWE-131 | 0.00161 | 0.53714 |
|
| CVE-2022-41888 | High 7.5 | CWE-20 | 0.00102 | 0.43008 |
|
| CVE-2022-41889 | High 7.5 | CWE-476 | 0.00128 | 0.48862 |
|
| CVE-2022-41890 | High 7.5 | CWE-704 | 0.00128 | 0.48862 |
|
| CVE-2022-41891 | High 7.5 | CWE-20 | 0.00102 | 0.43008 |
|
| CVE-2022-41893 | High 7.5 | CWE-617 | 0.00128 | 0.48862 |
|
| CVE-2022-41895 | High 7.5 | CWE-125 | 0.00128 | 0.48862 |
|
| CVE-2022-41896 | High 7.5 | CWE-1284, CWE-20 | 0.00102 | 0.43008 |
|
| CVE-2022-41897 | High 7.5 | CWE-125 | 0.00128 | 0.48862 |
|
| CVE-2022-41898 | High 7.5 | CWE-20 | 0.00102 | 0.43008 |
|
| CVE-2022-41899 | High 7.5 | CWE-20, CWE-617 | 0.00102 | 0.43008 |
|
| CVE-2022-41900 | High 9.8 | CWE-125, CWE-787 | 0.00131 | 0.49384 |
|
| CVE-2022-41901 | High 7.5 | CWE-20, CWE-617 | 0.00102 | 0.43008 |
|
| CVE-2022-41902 | High 9.1 | CWE-125, CWE-787 | 0.0014 | 0.5097 |
|
| CVE-2022-41907 | High 7.5 | CWE-131 | 0.00128 | 0.48862 |
|
| CVE-2022-41908 | High 7.5 | CWE-20 | 0.00102 | 0.43008 |
|
| CVE-2022-41909 | High 7.5 | CWE-20, CWE-476 | 0.00125 | 0.48467 |
|
| CVE-2022-41910 | High 9.1 | CWE-125 | 0.0014 | 0.5097 |
|
| CVE-2022-41911 | High 7.5 | CWE-704 | 0.00094 | 0.41325 |
|
| CVE-2023-25658 | High 7.5 | CWE-125 | 0.00091 | 0.40431 |
|
| CVE-2023-25659 | High 7.5 | CWE-125 | 0.00091 | 0.40431 |
|
| CVE-2023-25660 | High 7.5 | CWE-476 | 0.00091 | 0.40431 |
|
| CVE-2023-25662 | High 7.5 | CWE-190 | 0.00091 | 0.40431 |
|
| CVE-2023-25663 | High 7.5 | CWE-476 | 0.00089 | 0.39662 |
|
| CVE-2023-25664 | High 7.5 | CWE-122, CWE-120 | 0.00086 | 0.37827 |
|
| CVE-2023-25665 | High 7.5 | CWE-476 | 0.00087 | 0.38095 |
|
| CVE-2023-25666 | High 7.5 | CWE-697 | 0.00091 | 0.40431 |
|
| CVE-2023-25667 | High 7.5 | CWE-190 | 0.0013 | 0.49232 |
|
| CVE-2023-25668 | High 9.8 | CWE-125, CWE-122 | 0.00145 | 0.51678 |
|
| CVE-2023-25669 | High 7.5 | CWE-697 | 0.00091 | 0.40431 |
|
| CVE-2023-25670 | High 7.5 | CWE-476 | 0.00091 | 0.40431 |
|
| CVE-2023-25672 | High 7.5 | CWE-476 | 0.00091 | 0.40431 |
|
| CVE-2023-25673 | High 7.5 | CWE-697 | 0.00091 | 0.40431 |
|
| CVE-2023-25674 | High 7.5 | CWE-476 | 0.00089 | 0.39662 |
|
| CVE-2023-25675 | High 7.5 | CWE-697 | 0.00091 | 0.40431 |
|
| CVE-2023-25676 | High 7.5 | CWE-476 | 0.00091 | 0.40431 |
|
| CVE-2023-25801 | High 7.8 | CWE-415 | 0.00044 | 0.14048 |
|
| CVE-2023-27579 | High 7.5 | CWE-697 | 0.00091 | 0.40431 |
|
| CVE-2023-33976 | High 7.5 | CWE-190 | 0.00049 | 0.20291 |
|
| CVE-2018-8825 | High 8.8 | CWE-119 | 0.00176 | 0.55768 |
|
| CVE-2020-15212 | High 8.6 | CWE-787 | 0.0026 | 0.66504 |
|
| CVE-2020-15213 | Medium 4 | CWE-770 | 0.00124 | 0.48209 |
|
| CVE-2020-15214 | High 8.1 | CWE-787 | 0.0026 | 0.66504 |
|
| CVE-2021-29512 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29514 | High 7.8 | CWE-787 | 0.00048 | 0.19481 |
|
| CVE-2021-29521 | Medium 5.5 | CWE-131 | 0.00044 | 0.14248 |
|
| CVE-2021-29611 | Medium 5.5 | CWE-665, CWE-20 | 0.00044 | 0.14248 |
|
| CVE-2021-37680 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37681 | High 7.8 | CWE-476 | 0.00044 | 0.14048 |
|
| CVE-2021-37683 | Medium 5.5 | CWE-369 | 0.00044 | 0.14048 |
|
| CVE-2021-37687 | Medium 5.5 | CWE-125 | 0.00047 | 0.18673 |
|
| CVE-2021-29544 | Medium 5.5 | CWE-754 | 0.00086 | 0.38014 |
|
| CVE-2021-37692 | Medium 5.5 | CWE-20 | 0.00044 | 0.14048 |
|
| CVE-2021-41211 | High 7.1 | CWE-125 | 0.00048 | 0.19222 |
|
| CVE-2021-41220 | High 7.8 | CWE-416 | 0.00048 | 0.19222 |
|
| CVE-2022-23594 | Medium 5.5 | CWE-125, CWE-787 | 0.00044 | 0.14048 |
|
| CVE-2022-23592 | High 8.1 | CWE-125 | 0.00286 | 0.6949 |
|
| CVE-2022-23593 | High 7.5 | CWE-754 | 0.00192 | 0.57885 |
|
| CVE-2022-29210 | Medium 5.5 | CWE-122, CWE-787, CWE-120 | 0.00045 | 0.15555 |
|
| CVE-2022-41883 | High 7.5 | CWE-125 | 0.00161 | 0.53714 |
|
tensorflow-gpu Vulnerability Remediation Guidance
| CVE | Description | Full list of Impacted Versions | Fix |
|---|---|---|---|
| CVE-2023-33976 | TensorFlow is an end-to-end open source platform for machine learning. `array_ops.upper_bound` causes a segfault when not given a rank 2 tensor. The fix will be included in TensorFlow 2.13 and will also cherrypick this commit on TensorFlow 2.12. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-27579 | TensorFlow is an end-to-end open source platform for machine learning. Constructing a tflite model with a paramater `filter_input_channel` of less than 1 gives a FPE. This issue has been patched in version 2.12. TensorFlow will also cherrypick the fix commit on TensorFlow 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25801 | TensorFlow is an open source machine learning platform. Prior to versions 2.12.0 and 2.11.1, `nn_ops.fractional_avg_pool_v2` and `nn_ops.fractional_max_pool_v2` require the first and fourth elements of their parameter `pooling_ratio` to be equal to 1.0, as pooling on batch and channel dimensions is not supported. A fix is included in TensorFlow 2.12.0 and 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25676 | TensorFlow is an open source machine learning platform. When running versions prior to 2.12.0 and 2.11.1 with XLA, `tf.raw_ops.ParallelConcat` segfaults with a nullptr dereference when given a parameter `shape` with rank that is not greater than zero. A fix is available in TensorFlow 2.12.0 and 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25675 | TensorFlow is an open source machine learning platform. When running versions prior to 2.12.0 and 2.11.1 with XLA, `tf.raw_ops.Bincount` segfaults when given a parameter `weights` that is neither the same shape as parameter `arr` nor a length-0 tensor. A fix is included in TensorFlow 2.12.0 and 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25674 | TensorFlow is an open source machine learning platform. Versions prior to 2.12.0 and 2.11.1 have a null pointer error in RandomShuffle with XLA enabled. A fix is included in TensorFlow 2.12.0 and 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25673 | TensorFlow is an open source platform for machine learning. Versions prior to 2.12.0 and 2.11.1 have a Floating Point Exception in TensorListSplit with XLA. A fix is included in TensorFlow version 2.12.0 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25672 | TensorFlow is an open source platform for machine learning. The function `tf.raw_ops.LookupTableImportV2` cannot handle scalars in the `values` parameter and gives an NPE. A fix is included in TensorFlow version 2.12.0 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25670 | TensorFlow is an open source platform for machine learning. Versions prior to 2.12.0 and 2.11.1 have a null point error in QuantizedMatMulWithBiasAndDequantize with MKL enabled. A fix is included in TensorFlow version 2.12.0 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25669 | TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, if the stride and window size are not positive for `tf.raw_ops.AvgPoolGrad`, it can give a floating point exception. A fix is included in TensorFlow version 2.12.0 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25668 | TensorFlow is an open source platform for machine learning. Attackers using Tensorflow prior to 2.12.0 or 2.11.1 can access heap memory which is not in the control of user, leading to a crash or remote code execution. The fix will be included in TensorFlow version 2.12.0 and will also cherrypick this commit on TensorFlow version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25667 | TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, integer overflow occurs when `2^31 <= num_frames * height * width * channels < 2^32`, for example Full HD screencast of at least 346 frames. A fix is included in TensorFlow version 2.12.0 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25666 | TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25665 | TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, when `SparseSparseMaximum` is given invalid sparse tensors as inputs, it can give a null pointer error. A fix is included in TensorFlow version 2.12 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25664 | None | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25663 | TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, when `ctx->step_containter()` is a null ptr, the Lookup function will be executed with a null pointer. A fix is included in TensorFlow 2.12.0 and 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25662 | TensorFlow is an open source platform for machine learning. Versions prior to 2.12.0 and 2.11.1 are vulnerable to integer overflow in EditDistance. A fix is included in TensorFlow version 2.12.0 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25660 | TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, when the parameter `summarize` of `tf.raw_ops.Print` is zero, the new method `SummarizeArray<bool>` will reference to a nullptr, leading to a seg fault. A fix is included in TensorFlow version 2.12 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25659 | TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, if the parameter `indices` for `DynamicStitch` does not match the shape of the parameter `data`, it can trigger an stack OOB read. A fix is included in TensorFlow version 2.12.0 and version 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2023-25658 | TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, an out of bounds read is in GRUBlockCellGrad. A fix is included in TensorFlow 2.12.0 and 2.11.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41911 | TensorFlow is an open source platform for machine learning. When printing a tensor, we get it's data as a `const char*` array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from `char` to `bool` are undefined if the `char` is not `0` or `1`, so sanitizers/fuzzers will crash. The issue has been patched in GitHub commit `1be74370327`. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.10.1, TensorFlow 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41910 | TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41909 | TensorFlow is an open source platform for machine learning. An input `encoded` that is not a valid `CompositeTensorVariant` tensor will trigger a segfault in `tf.raw_ops.CompositeTensorVariantToComponents`. We have patched the issue in GitHub commits bf594d08d377dc6a3354d9fdb494b32d45f91971 and 660ce5a89eb6766834bdc303d2ab3902aef99d3d. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41908 | TensorFlow is an open source platform for machine learning. An input `token` that is not a UTF-8 bytestring will trigger a `CHECK` fail in `tf.raw_ops.PyFunc`. We have patched the issue in GitHub commit 9f03a9d3bafe902c1e6beb105b2f24172f238645. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41907 | TensorFlow is an open source platform for machine learning. When `tf.raw_ops.ResizeNearestNeighborGrad` is given a large `size` input, it overflows. We have patched the issue in GitHub commit 00c821af032ba9e5f5fa3fe14690c8d28a657624. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41902 | TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41901 | TensorFlow is an open source platform for machine learning. An input `sparse_matrix` that is not a matrix with a shape with rank 0 will trigger a `CHECK` fail in `tf.raw_ops.SparseMatrixNNZ`. We have patched the issue in GitHub commit f856d02e5322821aad155dad9b3acab1e9f5d693. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41900 | TensorFlow is an open source platform for machine learning. The security vulnerability results in FractionalMax(AVG)Pool with illegal pooling_ratio. Attackers using Tensorflow can exploit the vulnerability. They can access heap memory which is not in the control of user, leading to a crash or remote code execution. We have patched the issue in GitHub commit 216525144ee7c910296f5b05d214ca1327c9ce48. The fix will be included in TensorFlow 2.11.0. We will also cherry pick this commit on TensorFlow 2.10.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41899 | TensorFlow is an open source platform for machine learning. Inputs `dense_features` or `example_state_data` not of rank 2 will trigger a `CHECK` fail in `SdcaOptimizer`. We have patched the issue in GitHub commit 80ff197d03db2a70c6a111f97dcdacad1b0babfa. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41898 | TensorFlow is an open source platform for machine learning. If `SparseFillEmptyRowsGrad` is given empty inputs, TensorFlow will crash. We have patched the issue in GitHub commit af4a6a3c8b95022c351edae94560acc61253a1b8. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41897 | TensorFlow is an open source platform for machine learning. If `FractionMaxPoolGrad` is given outsize inputs `row_pooling_sequence` and `col_pooling_sequence`, TensorFlow will crash. We have patched the issue in GitHub commit d71090c3e5ca325bdf4b02eb236cfb3ee823e927. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41896 | TensorFlow is an open source platform for machine learning. If `ThreadUnsafeUnigramCandidateSampler` is given input `filterbank_channel_count` greater than the allowed max size, TensorFlow will crash. We have patched the issue in GitHub commit 39ec7eaf1428e90c37787e5b3fbd68ebd3c48860. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41895 | TensorFlow is an open source platform for machine learning. If `MirrorPadGrad` is given outsize input `paddings`, TensorFlow will give a heap OOB error. We have patched the issue in GitHub commit 717ca98d8c3bba348ff62281fdf38dcb5ea1ec92. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41893 | TensorFlow is an open source platform for machine learning. If `tf.raw_ops.TensorListResize` is given a nonscalar value for input `size`, it results `CHECK` fail which can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 888e34b49009a4e734c27ab0c43b0b5102682c56. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41891 | TensorFlow is an open source platform for machine learning. If `tf.raw_ops.TensorListConcat` is given `element_shape=[]`, it results segmentation fault which can be used to trigger a denial of service attack. We have patched the issue in GitHub commit fc33f3dc4c14051a83eec6535b608abe1d355fde. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41890 | TensorFlow is an open source platform for machine learning. If `BCast::ToShape` is given input larger than an `int32`, it will crash, despite being supposed to handle up to an `int64`. An example can be seen in `tf.experimental.numpy.outer` by passing in large input to the input `b`. We have patched the issue in GitHub commit 8310bf8dd188ff780e7fc53245058215a05bdbe5. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41889 | TensorFlow is an open source platform for machine learning. If a list of quantized tensors is assigned to an attribute, the pywrap code fails to parse the tensor and returns a `nullptr`, which is not caught. An example can be seen in `tf.compat.v1.extract_volume_patches` by passing in quantized tensors as input `ksizes`. We have patched the issue in GitHub commit e9e95553e5411834d215e6770c81a83a3d0866ce. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41888 | TensorFlow is an open source platform for machine learning. When running on GPU, `tf.image.generate_bounding_box_proposals` receives a `scores` input that must be of rank 4 but is not checked. We have patched the issue in GitHub commit cf35502463a88ca7185a99daa7031df60b3c1c98. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41887 | TensorFlow is an open source platform for machine learning. `tf.keras.losses.poisson` receives a `y_pred` and `y_true` that are passed through `functor::mul` in `BinaryOp`. If the resulting dimensions overflow an `int32`, TensorFlow will crash due to a size mismatch during broadcast assignment. We have patched the issue in GitHub commit c5b30379ba87cbe774b08ac50c1f6d36df4ebb7c. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1 and 2.9.3, as these are also affected and still in supported range. However, we will not cherrypick this commit into TensorFlow 2.8.x, as it depends on Eigen behavior that changed between 2.8 and 2.9. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41886 | TensorFlow is an open source platform for machine learning. When `tf.raw_ops.ImageProjectiveTransformV2` is given a large output shape, it overflows. We have patched the issue in GitHub commit 8faa6ea692985dbe6ce10e1a3168e0bd60a723ba. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41885 | TensorFlow is an open source platform for machine learning. When `tf.raw_ops.FusedResizeAndPadConv2D` is given a large tensor shape, it overflows. We have patched the issue in GitHub commit d66e1d568275e6a2947de97dca7a102a211e01ce. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41884 | TensorFlow is an open source platform for machine learning. If a numpy array is created with a shape such that one element is zero and the others sum to a large number, an error will be raised. We have patched the issue in GitHub commit 2b56169c16e375c521a3bc8ea658811cc0793784. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-41883 | TensorFlow is an open source platform for machine learning. When ops that have specified input sizes receive a differing number of inputs, the executor will crash. We have patched the issue in GitHub commit f5381e0e10b5a61344109c1b7c174c68110f7629. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 2.10.0 | Patch → NO_SAFE_VERSION |
| CVE-2022-41880 | TensorFlow is an open source platform for machine learning. When the `BaseCandidateSamplerOp` function receives a value in `true_classes` larger than `range_max`, a heap oob read occurs. We have patched the issue in GitHub commit b389f5c944cadfdfe599b3f1e4026e036f30d2d4. The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36027 | TensorFlow is an open source platform for machine learning. When converting transposed convolutions using per-channel weight quantization the converter segfaults and crashes the Python process. We have patched the issue in GitHub commit aa0b852a4588cea4d36b74feb05d93055540b450. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36026 | TensorFlow is an open source platform for machine learning. If `QuantizeAndDequantizeV3` is given a nonscalar `num_bits` input tensor, it results in a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit f3f9cb38ecfe5a8a703f2c4a8fead434ef291713. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36019 | TensorFlow is an open source platform for machine learning. If `FakeQuantWithMinMaxVarsPerChannel` is given `min` or `max` tensors of a rank other than one, it results in a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 785d67a78a1d533759fcd2f5e8d6ef778de849e0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36018 | TensorFlow is an open source platform for machine learning. If `RaggedTensorToVariant` is given a `rt_nested_splits` list that contains tensors of ranks other than one, it results in a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 88f93dfe691563baa4ae1e80ccde2d5c7a143821. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36017 | TensorFlow is an open source platform for machine learning. If `Requantize` is given `input_min`, `input_max`, `requested_output_min`, `requested_output_max` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 785d67a78a1d533759fcd2f5e8d6ef778de849e0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36016 | TensorFlow is an open source platform for machine learning. When `tensorflow::full_type::SubstituteFromAttrs` receives a `FullTypeDef& t` that is not exactly three args, it triggers a `CHECK`-fail instead of returning a status. We have patched the issue in GitHub commit 6104f0d4091c260ce9352f9155f7e9b725eab012. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36015 | TensorFlow is an open source platform for machine learning. When `RangeSize` receives values that do not fit into an `int64_t`, it crashes. We have patched the issue in GitHub commit 37e64539cd29fcfb814c4451152a60f5d107b0f0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36014 | TensorFlow is an open source platform for machine learning. When `mlir::tfg::TFOp::nameAttr` receives null type list attributes, it crashes. We have patched the issue in GitHub commits 3a754740d5414e362512ee981eefba41561a63a6 and a0f0b9a21c9270930457095092f558fbad4c03e5. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36013 | TensorFlow is an open source platform for machine learning. When `mlir::tfg::GraphDefImporter::ConvertNodeDef` tries to convert NodeDefs without an op name, it crashes. We have patched the issue in GitHub commit a0f0b9a21c9270930457095092f558fbad4c03e5. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36012 | TensorFlow is an open source platform for machine learning. When `mlir::tfg::ConvertGenericFunctionToFunctionDef` is given empty function attributes, it crashes. We have patched the issue in GitHub commit ad069af92392efee1418c48ff561fd3070a03d7b. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36011 | TensorFlow is an open source platform for machine learning. When `mlir::tfg::ConvertGenericFunctionToFunctionDef` is given empty function attributes, it gives a null dereference. We have patched the issue in GitHub commit 1cf45b831eeb0cab8655c9c7c5d06ec6f45fc41b. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36005 | TensorFlow is an open source platform for machine learning. When `tf.quantization.fake_quant_with_min_max_vars_gradient` receives input `min` or `max` that is nonscalar, it gives a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit f3cf67ac5705f4f04721d15e485e192bb319feed. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36004 | TensorFlow is an open source platform for machine learning. When `tf.random.gamma` receives large input shape and rates, it gives a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit 552bfced6ce4809db5f3ca305f60ff80dd40c5a3. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36003 | TensorFlow is an open source platform for machine learning. When `RandomPoissonV2` receives large input shape and rates, it gives a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit 552bfced6ce4809db5f3ca305f60ff80dd40c5a3. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36002 | TensorFlow is an open source platform for machine learning. When `Unbatch` receives a nonscalar input `id`, it gives a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit 4419d10d576adefa36b0e0a9425d2569f7c0189f. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36001 | TensorFlow is an open source platform for machine learning. When `DrawBoundingBoxes` receives an input `boxes` that is not of dtype `float`, it gives a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit da0d65cdc1270038e72157ba35bf74b85d9bda11. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-36000 | TensorFlow is an open source platform for machine learning. When `mlir::tfg::ConvertGenericFunctionToFunctionDef` is given empty function attributes, it gives a null dereference. We have patched the issue in GitHub commit aed36912609fc07229b4d0a7b44f3f48efc00fd0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35999 | TensorFlow is an open source platform for machine learning. When `Conv2DBackpropInput` receives empty `out_backprop` inputs (e.g. `[3, 1, 0, 1]`), the current CPU/GPU kernels `CHECK` fail (one with dnnl, the other with cudnn). This can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 27a65a43cf763897fecfa5cdb5cc653fc5dd0346. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35997 | TensorFlow is an open source platform for machine learning. If `tf.sparse.cross` receives an input `separator` that is not a scalar, it gives a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 83dcb4dbfa094e33db084e97c4d0531a559e0ebf. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35996 | TensorFlow is an open source platform for machine learning. If `Conv2D` is given empty `input` and the `filter` and `padding` sizes are valid, the output is all-zeros. This causes division-by-zero floating point exceptions that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 611d80db29dd7b0cfb755772c69d60ae5bca05f9. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35995 | TensorFlow is an open source platform for machine learning. When `AudioSummaryV2` receives an input `sample_rate` with more than one element, it gives a `CHECK` fails that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit bf6b45244992e2ee543c258e519489659c99fb7f. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35994 | TensorFlow is an open source platform for machine learning. When `CollectiveGather` receives an scalar input `input`, it gives a `CHECK` fails that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit c1f491817dec39a26be3c574e86a88c30f3c4770. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35993 | TensorFlow is an open source platform for machine learning. When `SetSize` receives an input `set_shape` that is not a 1D tensor, it gives a `CHECK` fails that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit cf70b79d2662c0d3c6af74583641e345fc939467. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35992 | TensorFlow is an open source platform for machine learning. When `TensorListFromTensor` receives an `element_shape` of a rank greater than one, it gives a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit 3db59a042a38f4338aa207922fa2f476e000a6ee. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35991 | TensorFlow is an open source platform for machine learning. When `TensorListScatter` and `TensorListScatterV2` receive an `element_shape` of a rank greater than one, they give a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit bb03fdf4aae944ab2e4b35c7daa051068a8b7f61. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35990 | TensorFlow is an open source platform for machine learning. When `tf.quantization.fake_quant_with_min_max_vars_per_channel_gradient` receives input `min` or `max` of rank other than 1, it gives a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit f3cf67ac5705f4f04721d15e485e192bb319feed. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range.There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35989 | TensorFlow is an open source platform for machine learning. When `MaxPool` receives a window size input array `ksize` with dimensions greater than its input tensor `input`, the GPU kernel gives a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 32d7bd3defd134f21a4e344c8dfd40099aaf6b18. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35988 | TensorFlow is an open source platform for machine learning. When `tf.linalg.matrix_rank` receives an empty input `a`, the GPU kernel gives a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit c55b476aa0e0bd4ee99d0f3ad18d9d706cd1260a. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35987 | TensorFlow is an open source platform for machine learning. `DenseBincount` assumes its input tensor `weights` to either have the same shape as its input tensor `input` or to be length-0. A different `weights` shape will trigger a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit bf4c14353c2328636a18bfad1e151052c81d5f43. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35985 | TensorFlow is an open source platform for machine learning. If `LRNGrad` is given an `output_image` input tensor that is not 4-D, it results in a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit bd90b3efab4ec958b228cd7cfe9125be1c0cf255. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35984 | TensorFlow is an open source platform for machine learning. `ParameterizedTruncatedNormal` assumes `shape` is of type `int32`. A valid `shape` of type `int64` results in a mismatched type `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 72180be03447a10810edca700cbc9af690dfeb51. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35983 | TensorFlow is an open source platform for machine learning. If `Save` or `SaveSlices` is run over tensors of an unsupported `dtype`, it results in a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 5dd7b86b84a864b834c6fa3d7f9f51c87efa99d4. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35982 | TensorFlow is an open source platform for machine learning. If `SparseBincount` is given inputs for `indices`, `values`, and `dense_shape` that do not make a valid sparse tensor, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 40adbe4dd15b582b0210dfbf40c243a62f5119fa. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35981 | TensorFlow is an open source platform for machine learning. `FractionalMaxPoolGrad` validates its inputs with `CHECK` failures instead of with returning errors. If it gets incorrectly sized inputs, the `CHECK` failure can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 8741e57d163a079db05a7107a7609af70931def4. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35979 | TensorFlow is an open source platform for machine learning. If `QuantizedRelu` or `QuantizedRelu6` are given nonscalar inputs for `min_features` or `max_features`, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 49b3824d83af706df0ad07e4e677d88659756d89. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35974 | TensorFlow is an open source platform for machine learning. If `QuantizeDownAndShrinkRange` is given nonscalar inputs for `input_min` or `input_max`, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 73ad1815ebcfeb7c051f9c2f7ab5024380ca8613. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35973 | TensorFlow is an open source platform for machine learning. If `QuantizedMatMul` is given nonscalar input for: `min_a`, `max_a`, `min_b`, or `max_b` It gives a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit aca766ac7693bf29ed0df55ad6bfcc78f35e7f48. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35972 | TensorFlow is an open source platform for machine learning. If `QuantizedBiasAdd` is given `min_input`, `max_input`, `min_bias`, `max_bias` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 785d67a78a1d533759fcd2f5e8d6ef778de849e0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35971 | TensorFlow is an open source platform for machine learning. If `FakeQuantWithMinMaxVars` is given `min` or `max` tensors of a nonzero rank, it results in a `CHECK` fail that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 785d67a78a1d533759fcd2f5e8d6ef778de849e0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35970 | TensorFlow is an open source platform for machine learning. If `QuantizedInstanceNorm` is given `x_min` or `x_max` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 785d67a78a1d533759fcd2f5e8d6ef778de849e0. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35969 | TensorFlow is an open source platform for machine learning. The implementation of `Conv2DBackpropInput` requires `input_sizes` to be 4-dimensional. Otherwise, it gives a `CHECK` failure which can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 50156d547b9a1da0144d7babe665cf690305b33c. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35968 | TensorFlow is an open source platform for machine learning. The implementation of `AvgPoolGrad` does not fully validate the input `orig_input_shape`. This results in a `CHECK` failure which can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 3a6ac52664c6c095aa2b114e742b0aa17fdce78f. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35967 | TensorFlow is an open source platform for machine learning. If `QuantizedAdd` is given `min_input` or `max_input` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 49b3824d83af706df0ad07e4e677d88659756d89. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35966 | TensorFlow is an open source platform for machine learning. If `QuantizedAvgPool` is given `min_input` or `max_input` tensors of a nonzero rank, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 7cdf9d4d2083b739ec81cfdace546b0c99f50622. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35965 | TensorFlow is an open source platform for machine learning. If `LowerBound` or `UpperBound` is given an empty`sorted_inputs` input, it results in a `nullptr` dereference, leading to a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit bce3717eaef4f769019fd18e990464ca4a2efeea. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35964 | TensorFlow is an open source platform for machine learning. The implementation of `BlockLSTMGradV2` does not fully validate its inputs. This results in a a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 2a458fc4866505be27c62f81474ecb2b870498fa. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35963 | TensorFlow is an open source platform for machine learning. The implementation of `FractionalAvgPoolGrad` does not fully validate the input `orig_input_tensor_shape`. This results in an overflow that results in a `CHECK` failure which can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 03a659d7be9a1154fdf5eeac221e5950fec07dad. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35960 | TensorFlow is an open source platform for machine learning. In `core/kernels/list_kernels.cc's TensorListReserve`, `num_elements` is assumed to be a tensor of size 1. When a `num_elements` of more than 1 element is provided, then `tf.raw_ops.TensorListReserve` fails the `CHECK_EQ` in `CheckIsAlignedAndSingleElement`. We have patched the issue in GitHub commit b5f6fbfba76576202b72119897561e3bd4f179c7. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35959 | TensorFlow is an open source platform for machine learning. The implementation of `AvgPool3DGradOp` does not fully validate the input `orig_input_shape`. This results in an overflow that results in a `CHECK` failure which can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 9178ac9d6389bdc54638ab913ea0e419234d14eb. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35952 | TensorFlow is an open source platform for machine learning. The `UnbatchGradOp` function takes an argument `id` that is assumed to be a scalar. A nonscalar `id` can trigger a `CHECK` failure and crash the program. It also requires its argument `batch_index` to contain three times the number of elements as indicated in its `batch_index.dim_size(0)`. An incorrect `batch_index` can trigger a `CHECK` failure and crash the program. We have patched the issue in GitHub commit 5f945fc6409a3c1e90d6970c9292f805f6e6ddf2. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35941 | TensorFlow is an open source platform for machine learning. The `AvgPoolOp` function takes an argument `ksize` that must be positive but is not checked. A negative `ksize` can trigger a `CHECK` failure and crash the program. We have patched the issue in GitHub commit 3a6ac52664c6c095aa2b114e742b0aa17fdce78f. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds to this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35940 | TensorFlow is an open source platform for machine learning. The `RaggedRangOp` function takes an argument `limits` that is eventually used to construct a `TensorShape` as an `int64`. If `limits` is a very large float, it can overflow when converted to an `int64`. This triggers an `InvalidArgument` but also throws an abort signal that crashes the program. We have patched the issue in GitHub commit 37cefa91bee4eace55715eeef43720b958a01192. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35939 | TensorFlow is an open source platform for machine learning. The `ScatterNd` function takes an input argument that determines the indices of of the output tensor. An input index greater than the output tensor or less than zero will either write content at the wrong index or trigger a crash. We have patched the issue in GitHub commit b4d4b4cb019bd7240a52daa4ba61e3cc814f0384. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35937 | TensorFlow is an open source platform for machine learning. The `GatherNd` function takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read is triggered. This issue has been patched in GitHub commit 595a65a3e224a0362d7e68c2213acfc2b499a196. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35935 | TensorFlow is an open source platform for machine learning. The implementation of SobolSampleOp is vulnerable to a denial of service via CHECK-failure (assertion failure) caused by assuming `input(0)`, `input(1)`, and `input(2)` to be scalar. This issue has been patched in GitHub commit c65c67f88ad770662e8f191269a907bf2b94b1bf. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-35934 | TensorFlow is an open source platform for machine learning. The implementation of tf.reshape op in TensorFlow is vulnerable to a denial of service via CHECK-failure (assertion failure) caused by overflowing the number of elements in a tensor. This issue has been patched in GitHub commit 61f0f9b94df8c0411f0ad0ecc2fec2d3f3c33555. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29216 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, TensorFlow's `saved_model_cli` tool is vulnerable to a code injection. This can be used to open a reverse shell. This code path was maintained for compatibility reasons as the maintainers had several test cases where numpy expressions were used as arguments. However, given that the tool is always run manually, the impact of this is still not severe. The maintainers have now removed the `safe=False` argument, so all parsing is done without calling `eval`. The patch is available in versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29213 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the `tf.compat.v1.signal.rfft2d` and `tf.compat.v1.signal.rfft3d` lack input validation and under certain condition can result in crashes (due to `CHECK`-failures). Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29212 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, certain TFLite models that were created using TFLite model converter would crash when loaded in the TFLite interpreter. The culprit is that during quantization the scale of values could be greater than 1 but code was always assuming sub-unit scaling. Thus, since code was calling `QuantizeMultiplierSmallerThanOneExp`, the `TFLITE_CHECK_LT` assertion would trigger and abort the process. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29211 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.histogram_fixed_width` is vulnerable to a crash when the values array contain `Not a Number` (`NaN`) elements. The implementation assumes that all floating point operations are defined and then converts a floating point result to an integer index. If `values` contains `NaN` then the result of the division is still `NaN` and the cast to `int32` would result in a crash. This only occurs on the CPU implementation. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29210 | TensorFlow is an open source platform for machine learning. In version 2.8.0, the `TensorKey` hash function used total estimated `AllocatedBytes()`, which (a) is an estimate per tensor, and (b) is a very poor hash function for constants (e.g. `int32_t`). It also tried to access individual tensor bytes through `tensor.data()` of size `AllocatedBytes()`. This led to ASAN failures because the `AllocatedBytes()` is an estimate of total bytes allocated by a tensor, including any pointed-to constructs (e.g. strings), and does not refer to contiguous bytes in the `.data()` buffer. The discoverers could not use this byte vector anyway because types such as `tstring` include pointers, whereas they needed to hash the string values themselves. This issue is patched in Tensorflow versions 2.9.0 and 2.8.1. | 2.8.0 | Patch → NO_SAFE_VERSION |
| CVE-2022-29209 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the macros that TensorFlow uses for writing assertions (e.g., `CHECK_LT`, `CHECK_GT`, etc.) have an incorrect logic when comparing `size_t` and `int` values. Due to type conversion rules, several of the macros would trigger incorrectly. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29208 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.EditDistance` has incomplete validation. Users can pass negative values to cause a segmentation fault based denial of service. In multiple places throughout the code, one may compute an index for a write operation. However, the existing validation only checks against the upper bound of the array. Hence, it is possible to write before the array by massaging the input to generate negative values for `loc`. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29207 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, multiple TensorFlow operations misbehave in eager mode when the resource handle provided to them is invalid. In graph mode, it would have been impossible to perform these API calls, but migration to TF 2.x eager mode opened up this vulnerability. If the resource handle is empty, then a reference is bound to a null pointer inside TensorFlow codebase (various codepaths). This is undefined behavior. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29206 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.SparseTensorDenseAdd` does not fully validate the input arguments. In this case, a reference gets bound to a `nullptr` during kernel execution. This is undefined behavior. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29205 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, there is a potential for segfault / denial of service in TensorFlow by calling `tf.compat.v1.*` ops which don't yet have support for quantized types, which was added after migration to TensorFlow 2.x. In these scenarios, since the kernel is missing, a `nullptr` value is passed to `ParseDimensionValue` for the `py_value` argument. Then, this is dereferenced, resulting in segfault. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29204 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.UnsortedSegmentJoin` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code assumes `num_segments` is a positive scalar but there is no validation. Since this value is used to allocate the output tensor, a negative value would result in a `CHECK`-failure (assertion failure), as per TFSA-2021-198. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29203 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.SpaceToBatchND` (in all backends such as XLA and handwritten kernels) is vulnerable to an integer overflow: The result of this integer overflow is used to allocate the output tensor, hence we get a denial of service via a `CHECK`-failure (assertion failure), as in TFSA-2021-198. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29202 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.ragged.constant` does not fully validate the input arguments. This results in a denial of service by consuming all available memory. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29201 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.QuantizedConv2D` does not fully validate the input arguments. In this case, references get bound to `nullptr` for each argument that is empty. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29200 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.LSTMBlockCell` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code does not validate the ranks of any of the arguments to this API call. This results in `CHECK`-failures when the elements of the tensor are accessed. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29199 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.LoadAndRemapMatrix does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code assumes `initializing_values` is a vector but there is no validation for this before accessing its value. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29198 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.SparseTensorToCSRSparseMatrix` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code assumes `dense_shape` is a vector and `indices` is a matrix (as part of requirements for sparse tensors) but there is no validation for this. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29197 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.UnsortedSegmentJoin` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code assumes `num_segments` is a scalar but there is no validation for this before accessing its value. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29196 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.Conv3DBackpropFilterV2` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code does not validate that the `filter_sizes` argument is a vector. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29195 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.StagePeek` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. The code assumes `index` is a scalar but there is no validation for this before accessing its value. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29194 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.DeleteSessionTensor` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29193 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.TensorSummaryV2` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29192 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-29191 | TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.GetSessionTensor` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23595 | Tensorflow is an Open Source Machine Learning Framework. When building an XLA compilation cache, if default settings are used, TensorFlow triggers a null pointer dereference. In the default scenario, all devices are allowed, so `flr->config_proto` is `nullptr`. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23594 | Tensorflow is an Open Source Machine Learning Framework. The TFG dialect of TensorFlow (MLIR) makes several assumptions about the incoming `GraphDef` before converting it to the MLIR-based dialect. If an attacker changes the `SavedModel` format on disk to invalidate these assumptions and the `GraphDef` is then converted to MLIR-based IR then they can cause a crash in the Python interpreter. Under certain scenarios, heap OOB read/writes are possible. These issues have been discovered via fuzzing and it is possible that more weaknesses exist. We will patch them as they are discovered. | 2.7.0 | Patch → NO_SAFE_VERSION |
| CVE-2022-23593 | Tensorflow is an Open Source Machine Learning Framework. The `simplifyBroadcast` function in the MLIR-TFRT infrastructure in TensorFlow is vulnerable to a segfault (hence, denial of service), if called with scalar shapes. If all shapes are scalar, then `maxRank` is 0, so we build an empty `SmallVector`. The fix will be included in TensorFlow 2.8.0. This is the only affected version. | 2.8.0rc0 | Patch → NO_SAFE_VERSION |
| CVE-2022-23592 | Tensorflow is an Open Source Machine Learning Framework. TensorFlow's type inference can cause a heap out of bounds read as the bounds checking is done in a `DCHECK` (which is a no-op during production). An attacker can control the `input_idx` variable such that `ix` would be larger than the number of values in `node_t.args`. The fix will be included in TensorFlow 2.8.0. This is the only affected version. | 2.8.0rc0 | Patch → NO_SAFE_VERSION |
| CVE-2022-23591 | Tensorflow is an Open Source Machine Learning Framework. The `GraphDef` format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a `GraphDef` containing a fragment such as the following can be consumed when loading a `SavedModel`. This would result in a stack overflow during execution as resolving each `NodeDef` means resolving the function itself and its nodes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23590 | Tensorflow is an Open Source Machine Learning Framework. A `GraphDef` from a TensorFlow `SavedModel` can be maliciously altered to cause a TensorFlow process to crash due to encountering a `StatusOr` value that is an error and forcibly extracting the value from it. We have patched the issue in multiple GitHub commits and these will be included in TensorFlow 2.8.0 and TensorFlow 2.7.1, as both are affected. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23589 | Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow can trigger a null pointer dereference. There are 2 places where this can occur, for the same malicious alteration of a `SavedModel` file (fixing the first one would trigger the same dereference in the second place). First, during constant folding, the `GraphDef` might not have the required nodes for the binary operation. If a node is missing, the correposning `mul_*child` would be null, and the dereference in the subsequent line would be incorrect. We have a similar issue during `IsIdentityConsumingSwitch`. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23588 | Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that Grappler optimizer would attempt to build a tensor using a reference `dtype`. This would result in a crash due to a `CHECK`-fail in the `Tensor` constructor as reference types are not allowed. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23587 | Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during cost estimation for crop and resize. Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23586 | Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that assertions in `function.cc` would be falsified and crash the Python interpreter. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23585 | Tensorflow is an Open Source Machine Learning Framework. When decoding PNG images TensorFlow can produce a memory leak if the image is invalid. After calling `png::CommonInitDecode(..., &decode)`, the `decode` value contains allocated buffers which can only be freed by calling `png::CommonFreeDecode(&decode)`. However, several error case in the function implementation invoke the `OP_REQUIRES` macro which immediately terminates the execution of the function, without allowing for the memory free to occur. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23584 | Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a use after free behavior when decoding PNG images. After `png::CommonFreeDecode(&decode)` gets called, the values of `decode.width` and `decode.height` are in an unspecified state. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23583 | Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that any binary op would trigger `CHECK` failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the `dtype` no longer matches the `dtype` expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If `Tin` and `Tout` don't match the type of data in `out` and `input_*` tensors then `flat<*>` would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a `CHECK` crash, hence a denial of service. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23582 | Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that `TensorByteSize` would trigger `CHECK` failures. `TensorShape` constructor throws a `CHECK`-fail if shape is partial or has a number of elements that would overflow the size of an `int`. The `PartialTensorShape` constructor instead does not cause a `CHECK`-abort if the shape is partial, which is exactly what this function needs to be able to return `-1`. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23581 | Tensorflow is an Open Source Machine Learning Framework. The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a `SavedModel` such that `IsSimplifiableReshape` would trigger `CHECK` failures. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23580 | Tensorflow is an Open Source Machine Learning Framework. During shape inference, TensorFlow can allocate a large vector based on a value from a tensor controlled by the user. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23579 | Tensorflow is an Open Source Machine Learning Framework. The Grappler optimizer in TensorFlow can be used to cause a denial of service by altering a `SavedModel` such that `SafeToRemoveIdentity` would trigger `CHECK` failures. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23578 | Tensorflow is an Open Source Machine Learning Framework. If a graph node is invalid, TensorFlow can leak memory in the implementation of `ImmutableExecutorState::Initialize`. Here, we set `item->kernel` to `nullptr` but it is a simple `OpKernel*` pointer so the memory that was previously allocated to it would leak. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23577 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `GetInitOp` is vulnerable to a crash caused by dereferencing a null pointer. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23576 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateOutputSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements. We can have a large enough number of dimensions in `output_shape.dim()` or just a small number of dimensions being large enough to cause an overflow in the multiplication. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23575 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `OpLevelCostEstimator::CalculateTensorSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve a tensor with large enough number of elements. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23574 | Tensorflow is an Open Source Machine Learning Framework. There is a typo in TensorFlow's `SpecializeType` which results in heap OOB read/write. Due to a typo, `arg` is initialized to the `i`th mutable argument in a loop where the loop index is `j`. Hence it is possible to assign to `arg` from outside the vector of arguments. Since this is a mutable proto value, it allows both read and write to outside of bounds data. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23573 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23572 | Tensorflow is an Open Source Machine Learning Framework. Under certain scenarios, TensorFlow can fail to specialize a type during shape inference. This case is covered by the `DCHECK` function however, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the `ValueOrDie` line. This results in an assertion failure as `ret` contains an error `Status`, not a value. In the second case we also get a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23571 | Tensorflow is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23570 | Tensorflow is an Open Source Machine Learning Framework. When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is guarded by a `DCHECK`. However, `DCHECK` is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23569 | Tensorflow is an Open Source Machine Learning Framework. Multiple operations in TensorFlow can be used to trigger a denial of service via `CHECK`-fails (i.e., assertion failures). This is similar to TFSA-2021-198 and has similar fixes. We have patched the reported issues in multiple GitHub commits. It is possible that other similar instances exist in TensorFlow, we will issue fixes as these are discovered. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23568 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `AddManySparseToTensorsMap` is vulnerable to an integer overflow which results in a `CHECK`-fail when building new `TensorShape` objects (so, an assert failure based denial of service). We are missing some validation on the shapes of the input tensors as well as directly constructing a large `TensorShape` with user-provided dimensions. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23567 | Tensorflow is an Open Source Machine Learning Framework. The implementations of `Sparse*Cwise*` ops are vulnerable to integer overflows. These can be used to trigger large allocations (so, OOM based denial of service) or `CHECK`-fails when building new `TensorShape` objects (so, assert failures based denial of service). We are missing some validation on the shapes of the input tensors as well as directly constructing a large `TensorShape` with user-provided dimensions. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23566 | Tensorflow is an Open Source Machine Learning Framework. TensorFlow is vulnerable to a heap OOB write in `Grappler`. The `set_output` function writes to an array at the specified index. Hence, this gives a malicious user a write primitive. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23565 | Tensorflow is an Open Source Machine Learning Framework. An attacker can trigger denial of service via assertion failure by altering a `SavedModel` on disk such that `AttrDef`s of some operation are duplicated. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23564 | Tensorflow is an Open Source Machine Learning Framework. When decoding a resource handle tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments. This allows attackers to cause denial of services in TensorFlow processes. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23563 | Tensorflow is an Open Source Machine Learning Framework. In multiple places, TensorFlow uses `tempfile.mktemp` to create temporary files. While this is acceptable in testing, in utilities and libraries it is dangerous as a different process can create the file between the check for the filename in `mktemp` and the actual creation of the file by a subsequent operation (a TOC/TOU type of weakness). In several instances, TensorFlow was supposed to actually create a temporary directory instead of a file. This logic bug is hidden away by the `mktemp` function usage. We have patched the issue in several commits, replacing `mktemp` with the safer `mkstemp`/`mkdtemp` functions, according to the usage pattern. Users are advised to upgrade as soon as possible. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23562 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `Range` suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23561 | Tensorflow is an Open Source Machine Learning Framework. An attacker can craft a TFLite model that would cause a write outside of bounds of an array in TFLite. In fact, the attacker can override the linked list used by the memory allocator. This can be leveraged for an arbitrary write primitive under certain conditions. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23560 | Tensorflow is an Open Source Machine Learning Framework. An attacker can craft a TFLite model that would allow limited reads and writes outside of arrays in TFLite. This exploits missing validation in the conversion from sparse tensors to dense tensors. The fix is included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. Users are advised to upgrade as soon as possible. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23559 | Tensorflow is an Open Source Machine Learning Framework. An attacker can craft a TFLite model that would cause an integer overflow in embedding lookup operations. Both `embedding_size` and `lookup_size` are products of values provided by the user. Hence, a malicious user could trigger overflows in the multiplication. In certain scenarios, this can then result in heap OOB read/write. Users are advised to upgrade to a patched version. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23558 | Tensorflow is an Open Source Machine Learning Framework. An attacker can craft a TFLite model that would cause an integer overflow in `TfLiteIntArrayCreate`. The `TfLiteIntArrayGetSizeInBytes` returns an `int` instead of a `size_t. An attacker can control model inputs such that `computed_size` overflows the size of `int` datatype. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-23557 | Tensorflow is an Open Source Machine Learning Framework. An attacker can craft a TFLite model that would trigger a division by zero in `BiasAndClamp` implementation. There is no check that the `bias_size` is non zero. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21741 | Tensorflow is an Open Source Machine Learning Framework. ### Impact An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions. The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is strictly positive. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21740 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `SparseCountSparseOutput` is vulnerable to a heap overflow. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21739 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `QuantizedMaxPool` has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21738 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `SparseCountSparseOutput` can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21737 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `*Bincount` operations allows malicious users to cause denial of service by passing in arguments which would trigger a `CHECK`-fail. There are several conditions that the input arguments must satisfy. Some are not caught during shape inference and others are not caught during kernel implementation. This results in `CHECK` failures later when the output tensors get allocated. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21736 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `SparseTensorSliceDataset` has an undefined behavior: under certain condition it can be made to dereference a `nullptr` value. The 3 input arguments to `SparseTensorSliceDataset` represent a sparse tensor. However, there are some preconditions that these arguments must satisfy but these are not validated in the implementation. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21735 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `FractionalMaxPool` can be made to crash a TensorFlow process via a division by 0. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21734 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `MapStage` is vulnerable a `CHECK`-fail if the key tensor is not a scalar. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21733 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `StringNGrams` can be used to trigger a denial of service attack by causing an out of memory condition after an integer overflow. We are missing a validation on `pad_witdh` and that result in computing a negative value for `ngram_width` which is later used to allocate parts of the output. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21732 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `ThreadPoolHandle` can be used to trigger a denial of service attack by allocating too much memory. This is because the `num_threads` argument is only checked to not be negative, but there is no upper bound on its value. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21731 | Tensorflow is an Open Source Machine Learning Framework. The implementation of shape inference for `ConcatV2` can be used to trigger a denial of service attack via a segfault caused by a type confusion. The `axis` argument is translated into `concat_dim` in the `ConcatShapeHelper` helper function. Then, a value for `min_rank` is computed based on `concat_dim`. This is then used to validate that the `values` tensor has at least the required rank. However, `WithRankAtLeast` receives the lower bound as a 64-bits value and then compares it against the maximum 32-bits integer value that could be represented. Due to the fact that `min_rank` is a 32-bits value and the value of `axis`, the `rank` argument is a negative value, so the error check is bypassed. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21730 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `FractionalAvgPoolGrad` does not consider cases where the input tensors are invalid allowing an attacker to read from outside of bounds of heap. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21729 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `UnravelIndex` is vulnerable to a division by zero caused by an integer overflow bug. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21728 | Tensorflow is an Open Source Machine Learning Framework. The implementation of shape inference for `ReverseSequence` does not fully validate the value of `batch_dim` and can result in a heap OOB read. There is a check to make sure the value of `batch_dim` does not go over the rank of the input, but there is no check for negative values. Negative dimensions are allowed in some cases to mimic Python's negative indexing (i.e., indexing from the end of the array), however if the value is too negative then the implementation of `Dim` would access elements before the start of an array. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21727 | Tensorflow is an Open Source Machine Learning Framework. The implementation of shape inference for `Dequantize` is vulnerable to an integer overflow weakness. The `axis` argument can be `-1` (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked, and, since the code computes `axis + 1`, an attacker can trigger an integer overflow. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21726 | Tensorflow is an Open Source Machine Learning Framework. The implementation of `Dequantize` does not fully validate the value of `axis` and can result in heap OOB accesses. The `axis` argument can be `-1` (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked and this results in reading past the end of the array containing the dimensions of the input tensor. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2022-21725 | Tensorflow is an Open Source Machine Learning Framework. The estimator for the cost of some convolution operations can be made to execute a division by 0. The function fails to check that the stride argument is strictly positive. Hence, the fix is to add a check for the stride argument to ensure it is valid. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41228 | TensorFlow is an open source platform for machine learning. In affected versions TensorFlow's `saved_model_cli` tool is vulnerable to a code injection as it calls `eval` on user supplied strings. This can be used by attackers to run arbitrary code on the plaform where the CLI tool runs. However, given that the tool is always run manually, the impact of this is not severe. We have patched this by adding a `safe` flag which defaults to `True` and an explicit warning for users. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41227 | TensorFlow is an open source platform for machine learning. In affected versions the `ImmutableConst` operation in TensorFlow can be tricked into reading arbitrary memory contents. This is because the `tstring` TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41226 | TensorFlow is an open source platform for machine learning. In affected versions the implementation of `SparseBinCount` is vulnerable to a heap OOB access. This is because of missing validation between the elements of the `values` argument and the shape of the sparse output. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41225 | TensorFlow is an open source platform for machine learning. In affected versions TensorFlow's Grappler optimizer has a use of unitialized variable. If the `train_nodes` vector (obtained from the saved model that gets optimized) does not contain a `Dequeue` node, then `dequeue_node` is left unitialized. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41224 | TensorFlow is an open source platform for machine learning. In affected versions the implementation of `SparseFillEmptyRows` can be made to trigger a heap OOB access. This occurs whenever the size of `indices` does not match the size of `values`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41223 | TensorFlow is an open source platform for machine learning. In affected versions the implementation of `FusedBatchNorm` kernels is vulnerable to a heap OOB access. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41222 | TensorFlow is an open source platform for machine learning. In affected versions the implementation of `SplitV` can trigger a segfault is an attacker supplies negative arguments. This occurs whenever `size_splits` contains more than one value and at least one value is negative. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41221 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for the `Cudnn*` operations in TensorFlow can be tricked into accessing invalid memory, via a heap buffer overflow. This occurs because the ranks of the `input`, `input_h` and `input_c` parameters are not validated, but code assumes they have certain values. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41220 | TensorFlow is an open source platform for machine learning. In affected versions the async implementation of `CollectiveReduceV2` suffers from a memory leak and a use after free. This occurs due to the asynchronous computation and the fact that objects that have been `std::move()`d from are still accessed. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected. | 2.6.0, 2.7.0rc0, 2.7.0rc1 | Patch → NO_SAFE_VERSION |
| CVE-2021-41219 | TensorFlow is an open source platform for machine learning. In affected versions the code for sparse matrix multiplication is vulnerable to undefined behavior via binding a reference to `nullptr`. This occurs whenever the dimensions of `a` or `b` are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41218 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `AllToAll` can be made to execute a division by 0. This occurs whenever the `split_count` argument is 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41217 | TensorFlow is an open source platform for machine learning. In affected versions the process of building the control flow graph for a TensorFlow model is vulnerable to a null pointer exception when nodes that should be paired are not. This occurs because the code assumes that the first node in the pairing (e.g., an `Enter` node) always exists when encountering the second node (e.g., an `Exit` node). When this is not the case, `parent` is `nullptr` so dereferencing it causes a crash. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41216 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference function for `Transpose` is vulnerable to a heap buffer overflow. This occurs whenever `perm` contains negative elements. The shape inference function does not validate that the indices in `perm` are all valid. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41215 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `DeserializeSparse` can trigger a null pointer dereference. This is because the shape inference function assumes that the `serialize_sparse` tensor is a tensor with positive rank (and having `3` as the last dimension). 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41214 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `tf.ragged.cross` has an undefined behavior due to binding a reference to `nullptr`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41213 | 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41212 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `tf.ragged.cross` can trigger a read outside of bounds of heap allocated array. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41211 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `QuantizeV2` can trigger a read outside of bounds of heap allocated array. This occurs whenever `axis` is a negative value less than `-1`. In this case, we are accessing data before the start of a heap buffer. The code allows `axis` to be an optional argument (`s` would contain an `error::NOT_FOUND` error code). Otherwise, it assumes that `axis` is a valid index into the dimensions of the `input` tensor. If `axis` is less than `-1` then this results in a heap OOB read. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected. | 2.6.0, 2.7.0rc0, 2.7.0rc1 | Patch → NO_SAFE_VERSION |
| CVE-2021-41210 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference functions for `SparseCountSparseOutput` can trigger a read outside of bounds of heap allocated array. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41209 | TensorFlow is an open source platform for machine learning. In affected versions the implementations for convolution operators trigger a division by 0 if passed empty filter tensor arguments. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41208 | TensorFlow is an open source platform for machine learning. In affected versions the code for boosted trees in TensorFlow is still missing validation. As a result, attackers can trigger denial of service (via dereferencing `nullptr`s or via `CHECK`-failures) as well as abuse undefined behavior (binding references to `nullptr`s). An attacker can also read and write from heap buffers, depending on the API that gets used and the arguments that are passed to the call. Given that the boosted trees implementation in TensorFlow is unmaintained, it is recommend to no longer use these APIs. We will deprecate TensorFlow's boosted trees APIs in subsequent releases. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41207 | TensorFlow is an open source platform for machine learning. In affected versions the implementation of `ParallelConcat` misses some input validation and can produce a division by 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41206 | TensorFlow is an open source platform for machine learning. In affected versions several TensorFlow operations are missing validation for the shapes of the tensor arguments involved in the call. Depending on the API, this can result in undefined behavior and segfault or `CHECK`-fail related crashes but in some scenarios writes and reads from heap populated arrays are also possible. We have discovered these issues internally via tooling while working on improving/testing GPU op determinism. As such, we don't have reproducers and there will be multiple fixes for these issues. These fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41205 | TensorFlow is an open source platform for machine learning. In affected versions the shape inference functions for the `QuantizeAndDequantizeV*` operations can trigger a read outside of bounds of heap allocated array. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41204 | TensorFlow is an open source platform for machine learning. In affected versions during TensorFlow's Grappler optimizer phase, constant folding might attempt to deep copy a resource tensor. This results in a segfault, as these tensors are supposed to not change. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41203 | TensorFlow is an open source platform for machine learning. In affected versions an attacker can trigger undefined behavior, integer overflows, segfaults and `CHECK`-fail crashes if they can change saved checkpoints from outside of TensorFlow. This is because the checkpoints loading infrastructure is missing validation for invalid file formats. The fixes will be included in TensorFlow 2.7.0. We will also cherrypick these commits on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41202 | TensorFlow is an open source platform for machine learning. In affected versions while calculating the size of the output within the `tf.range` kernel, there is a conditional statement of type `int64 = condition ? int64 : double`. Due to C++ implicit conversion rules, both branches of the condition will be cast to `double` and the result would be truncated before the assignment. This result in overflows. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41201 | TensorFlow is an open source platform for machine learning. In affeced versions during execution, `EinsumHelper::ParseEquation()` is supposed to set the flags in `input_has_ellipsis` vector and `*output_has_ellipsis` boolean to indicate whether there is ellipsis in the corresponding inputs and output. However, the code only changes these flags to `true` and never assigns `false`. This results in unitialized variable access if callers assume that `EinsumHelper::ParseEquation()` always sets these flags. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41200 | TensorFlow is an open source platform for machine learning. In affected versions if `tf.summary.create_file_writer` is called with non-scalar arguments code crashes due to a `CHECK`-fail. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41199 | TensorFlow is an open source platform for machine learning. In affected versions if `tf.image.resize` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow. The number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41198 | TensorFlow is an open source platform for machine learning. In affected versions if `tf.tile` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow. The number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41197 | TensorFlow is an open source platform for machine learning. In affected versions TensorFlow allows tensor to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an `int64_t`. If an overflow occurs, `MultiplyWithoutOverflow` would return a negative result. In the majority of TensorFlow codebase this then results in a `CHECK`-failure. Newer constructs exist which return a `Status` instead of crashing the binary. This is similar to CVE-2021-29584. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41196 | TensorFlow is an open source platform for machine learning. In affected versions the Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative. This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-41195 | TensorFlow is an open source platform for machine learning. In affected versions the implementation of `tf.math.segment_*` operations results in a `CHECK`-fail related abort (and denial of service) if a segment id in `segment_ids` is large. This is similar to CVE-2021-29584 (and similar other reported vulnerabilities in TensorFlow, localized to specific APIs): the implementation (both on CPU and GPU) computes the output shape using `AddDim`. However, if the number of elements in the tensor overflows an `int64_t` value, `AddDim` results in a `CHECK` failure which provokes a `std::abort`. Instead, code should use `AddDimWithStatus`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| 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. | 2.5.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-37691 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can craft a TFLite model that would trigger a division by zero error in LSH [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/lsh_projection.cc#L118). We have patched the issue in GitHub commit 0575b640091680cfb70f4dd93e70658de43b94f9. The fix will be included in TensorFlow 2.6.0. We will also cherrypick thiscommit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37690 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions when running shape functions, some functions (such as `MutableHashTableShape`) produce extra output information in the form of a `ShapeAndType` struct. The shapes embedded in this struct are owned by an inference context that is cleaned up almost immediately; if the upstream code attempts to access this shape information, it can trigger a segfault. `ShapeRefiner` is mitigating this for normal output shapes by cloning them (and thus putting the newly created shape under ownership of an inference context that will not die), but we were not doing the same for shapes and types. This commit fixes that by doing similar logic on output shapes and types. We have patched the issue in GitHub commit ee119d4a498979525046fba1c3dd3f13a039fbb1. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37689 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. This is caused by the MLIR optimization of `L2NormalizeReduceAxis` operator. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/compiler/mlir/lite/transforms/optimize.cc#L67-L70) unconditionally dereferences a pointer to an iterator to a vector without checking that the vector has elements. We have patched the issue in GitHub commit d6b57f461b39fd1aa8c1b870f1b974aac3554955. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37688 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can craft a TFLite model that would trigger a null pointer dereference, which would result in a crash and denial of service. The [implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L268-L285) unconditionally dereferences a pointer. We have patched the issue in GitHub commit 15691e456c7dc9bd6be203b09765b063bf4a380c. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37687 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions TFLite's [`GatherNd` implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather_nd.cc#L124) does not support negative indices but there are no checks for this situation. Hence, an attacker can read arbitrary data from the heap by carefully crafting a model with negative values in `indices`. Similar issue exists in [`Gather` implementation](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/gather.cc). We have patched the issue in GitHub commits bb6a0383ed553c286f87ca88c207f6774d5c4a8f and eb921122119a6b6e470ee98b89e65d721663179d. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 2.3.0, 2.3.2, 2.3.3, 2.3.1, 2.4.1, 2.4.0, 2.4.2, 2.5.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-37686 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop. We have patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695. TensorFlow 2.6.0 is the only affected version. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37685 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions TFLite's [`expand_dims.cc`](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/expand_dims.cc#L36-L50) contains a vulnerability which allows reading one element outside of bounds of heap allocated data. If `axis` is a large negative value (e.g., `-100000`), then after the first `if` it would still be negative. The check following the `if` statement will pass and the `for` loop would read one element before the start of `input_dims.data` (when `i = 0`). We have patched the issue in GitHub commit d94ffe08a65400f898241c0374e9edc6fa8ed257. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37684 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementations of pooling in TFLite are vulnerable to division by 0 errors as there are no checks for divisors not being 0. We have patched the issue in GitHub commit [dfa22b348b70bb89d6d6ec0ff53973bacb4f4695](https://github.com/tensorflow/tensorflow/commit/dfa22b348b70bb89d6d6ec0ff53973bacb4f4695). The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37683 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of division in TFLite is [vulnerable to a division by 0 error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc). There is no check that the divisor tensor does not contain zero elements. We have patched the issue in GitHub commit 1e206baedf8bef0334cca3eb92bab134ef525a28. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 2.3.0, 2.3.2, 2.3.3, 2.3.1, 2.4.1, 2.4.0, 2.4.2, 2.5.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-37682 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions all TFLite operations that use quantization can be made to use unitialized values. [For example](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). The issue stems from the fact that `quantization.params` is only valid if `quantization.type` is different that `kTfLiteNoQuantization`. However, these checks are missing in large parts of the code. We have patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37681 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of SVDF in TFLite is [vulnerable to a null pointer error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313). The [`GetVariableInput` function](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but `GetTensorData` assumes that the argument is always a valid tensor. Furthermore, because `GetVariableInput` calls [`GetMutableInput`](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return `nullptr`, the `tensor->is_variable` expression can also trigger a null pointer exception. We have patched the issue in GitHub commit 5b048e87e4e55990dae6b547add4dae59f4e1c76. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 2.3.0, 2.3.2, 2.3.3, 2.3.1, 2.4.1, 2.4.0, 2.4.2, 2.5.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-37680 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of fully connected layers in TFLite is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/fully_connected.cc#L226). We have patched the issue in GitHub commit 718721986aa137691ee23f03638867151f74935f. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 2.3.0, 2.3.2, 2.3.3, 2.3.1, 2.4.1, 2.4.0, 2.4.2, 2.5.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-37679 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions it is possible to nest a `tf.map_fn` within another `tf.map_fn` call. However, if the input tensor is a `RaggedTensor` and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap. The `t` and `z` outputs should be identical, however this is not the case. The last row of `t` contains data from the heap which can be used to leak other memory information. The bug lies in the conversion from a `Variant` tensor to a `RaggedTensor`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions. The same implementation can result in data loss, if input tensor is tweaked. We have patched the issue in GitHub commit 4e2565483d0ffcadc719bd44893fb7f609bb5f12. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37678 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input. Given that YAML format support requires a significant amount of work, we have removed it for now. We have patched the issue in GitHub commit 23d6383eb6c14084a8fc3bdf164043b974818012. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37677 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the shape inference code for `tf.raw_ops.Dequantize` has a vulnerability that could trigger a denial of service via a segfault if an attacker provides invalid arguments. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/array_ops.cc#L2999-L3014) uses `axis` to select between two different values for `minmax_rank` which is then used to retrieve tensor dimensions. However, code assumes that `axis` can be either `-1` or a value greater than `-1`, with no validation for the other values. We have patched the issue in GitHub commit da857cfa0fde8f79ad0afdbc94e88b5d4bbec764. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37676 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.SparseFillEmptyRows`. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/ops/sparse_ops.cc#L608-L634) does not validate that the input arguments are not empty tensors. We have patched the issue in GitHub commit 578e634b4f1c1c684d4b4294f9e5281b2133b3ed. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37675 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions most implementations of convolution operators in TensorFlow are affected by a division by 0 vulnerability where an attacker can trigger a denial of service via a crash. The shape inference [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/framework/common_shape_fns.cc#L577) is missing several validations before doing divisions and modulo operations. We have patched the issue in GitHub commit 8a793b5d7f59e37ac7f3cd0954a750a2fe76bad4. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37674 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a denial of service via a segmentation fault in `tf.raw_ops.MaxPoolGrad` caused by missing validation. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/maxpooling_op.cc) misses some validation for the `orig_input` and `orig_output` tensors. The fixes for CVE-2021-29579 were incomplete. We have patched the issue in GitHub commit 136b51f10903e044308cf77117c0ed9871350475. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37673 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.MapStage`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the `key` input is a valid non-empty tensor. We have patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37672 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.SdcaOptimizerV2`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/sdca_internal.cc#L320-L353) does not check that the length of `example_labels` is the same as the number of examples. We have patched the issue in GitHub commit a4e138660270e7599793fa438cd7b2fc2ce215a6. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37671 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that `indices` is in ascending order, but does not check that `indices` is not empty. We have patched the issue in GitHub commit 532f5c5a547126c634fefd43bbad1dc6417678ac. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37670 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.UpperBound`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of `sorted_input` argument. A similar issue occurs in `tf.raw_ops.LowerBound`. We have patched the issue in GitHub commit 42459e4273c2e47a3232cc16c4f4fff3b3a35c38. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37669 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause denial of service in applications serving models using `tf.raw_ops.NonMaxSuppressionV5` by triggering a division by 0. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/image/non_max_suppression_op.cc#L170-L271) uses a user controlled argument to resize a `std::vector`. However, as `std::vector::resize` takes the size argument as a `size_t` and `output_size` is an `int`, there is an implicit conversion to unsigned. If the attacker supplies a negative value, this conversion results in a crash. A similar issue occurs in `CombinedNonMaxSuppression`. We have patched the issue in GitHub commit 3a7362750d5c372420aa8f0caf7bf5b5c3d0f52d and commit [b5cdbf12ffcaaffecf98f22a6be5a64bb96e4f58. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37668 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause denial of service in applications serving models using `tf.raw_ops.UnravelIndex` by triggering a division by 0. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by `dims` is not empty. Hence, if one element of `dims` is 0, the implementation does a division by 0. We have patched the issue in GitHub commit a776040a5e7ebf76eeb7eb923bf1ae417dd4d233. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37667 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.UnicodeEncode`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unicode_ops.cc#L533-L539) reads the first dimension of the `input_splits` tensor before validating that this tensor is not empty. We have patched the issue in GitHub commit 2e0ee46f1a47675152d3d865797a18358881d7a6. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37666 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToVariant`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L129) has an incomplete validation of the splits values, missing the case when the argument would be empty. We have patched the issue in GitHub commit be7a4de6adfbd303ce08be4332554dff70362612. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37665 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions due to incomplete validation in MKL implementation of requantization, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantization_range_per_channel_op.cc) does not validate the dimensions of the `input` tensor. A similar issue occurs in `MklRequantizePerChannelOp`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/mkl/mkl_requantize_per_channel_op.cc) does not perform full validation for all the input arguments. We have patched the issue in GitHub commit 9e62869465573cb2d9b5053f1fa02a81fce21d69 and in the Github commit 203214568f5bc237603dbab6e1fd389f1572f5c9. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37664 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `BoostedTreesSparseCalculateBestFeatureSplit`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) needs to validate that each value in `stats_summary_indices` is in range. We have patched the issue in GitHub commit e84c975313e8e8e38bb2ea118196369c45c51378. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37663 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions due to incomplete validation in `tf.raw_ops.QuantizeV2`, an attacker can trigger undefined behavior via binding a reference to a null pointer or can access data outside the bounds of heap allocated arrays. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/quantize_op.cc#L59) has some validation but does not check that `min_range` and `max_range` both have the same non-zero number of elements. If `axis` is provided (i.e., not `-1`), then validation should check that it is a value in range for the rank of `input` tensor and then the lengths of `min_range` and `max_range` inputs match the `axis` dimension of the `input` tensor. We have patched the issue in GitHub commit 6da6620efad397c85493b8f8667b821403516708. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37662 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can generate undefined behavior via a reference binding to nullptr in `BoostedTreesCalculateBestGainsPerFeature` and similar attack can occur in `BoostedTreesCalculateBestFeatureSplitV2`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values. We have patched the issue in GitHub commit 9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad and in commit 429f009d2b2c09028647dd4bb7b3f6f414bbaad7. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37661 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause a denial of service in `boosted_trees_create_quantile_stream_resource` by using negative arguments. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantile_ops.cc#L96) does not validate that `num_streams` only contains non-negative numbers. In turn, [this results in using this value to allocate memory](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/quantiles/quantile_stream_resource.h#L31-L40). However, `reserve` receives an unsigned integer so there is an implicit conversion from a negative value to a large positive unsigned. This results in a crash from the standard library. We have patched the issue in GitHub commit 8a84f7a2b5a2b27ecf88d25bad9ac777cd2f7992. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37660 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause a floating point exception by calling inplace operations with crafted arguments that would result in a division by 0. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/inplace_ops.cc#L283) has a logic error: it should skip processing if `x` and `v` are empty but the code uses `||` instead of `&&`. We have patched the issue in GitHub commit e86605c0a336c088b638da02135ea6f9f6753618. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37659 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all binary cwise operations that don't require broadcasting (e.g., gradients of binary cwise operations). The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/cwise_ops_common.h#L264) assumes that the two inputs have exactly the same number of elements but does not check that. Hence, when the eigen functor executes it triggers heap OOB reads and undefined behavior due to binding to nullptr. We have patched the issue in GitHub commit 93f428fd1768df147171ed674fee1fc5ab8309ec. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37658 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixSetDiagV*`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. We have patched the issue in GitHub commit ff8894044dfae5568ecbf2ed514c1a37dc394f1b. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37657 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in all operations of type `tf.raw_ops.MatrixDiagV*`. The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/linalg/matrix_diag_op.cc) has incomplete validation that the value of `k` is a valid tensor. We have check that this value is either a scalar or a vector, but there is no check for the number of elements. If this is an empty tensor, then code that accesses the first element of the tensor is wrong. We have patched the issue in GitHub commit f2a673bd34f0d64b8e40a551ac78989d16daad09. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37656 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.RaggedTensorToSparse`. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/ragged_tensor_to_sparse_kernel.cc#L30) has an incomplete validation of the splits values: it does not check that they are in increasing order. We have patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37655 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. We have patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37654 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a crash via a `CHECK`-fail in debug builds of TensorFlow using `tf.raw_ops.ResourceGather` or a read from outside the bounds of heap allocated data in the same API in a release build. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L660-L668) does not check that the `batch_dims` value that the user supplies is less than the rank of the input tensor. Since the implementation uses several for loops over the dimensions of `tensor`, this results in reading data from outside the bounds of heap allocated buffer backing the tensor. We have patched the issue in GitHub commit bc9c546ce7015c57c2f15c168b3d9201de679a1d. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37653 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a crash via a floating point exception in `tf.raw_ops.ResourceGather`. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, `batch_size`, and then divides by it without checking that this value is not 0. We have patched the issue in GitHub commit ac117ee8a8ea57b73d34665cdf00ef3303bc0b11. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37652 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation for `tf.raw_ops.BoostedTreesCreateEnsemble` can result in a use after free error if an attacker supplies specially crafted arguments. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent `free`-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed. We have patched the issue in GitHub commit 5ecec9c6fbdbc6be03295685190a45e7eee726ab. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37651 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation for `tf.raw_ops.FractionalAvgPoolGrad` can be tricked into accessing data outside of bounds of heap allocated buffers. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty `EigenDoubleMatrixMap` and then accesses this buffer with indices that are outside of the empty area. We have patched the issue in GitHub commit 0f931751fb20f565c4e94aa6df58d54a003cdb30. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37650 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation for `tf.raw_ops.ExperimentalDatasetToTFRecord` and `tf.raw_ops.DatasetToTFRecord` can trigger heap buffer overflow and segmentation fault. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/to_tf_record_op.cc#L93-L102) assumes that all records in the dataset are of string type. However, there is no check for that, and the example given above uses numeric types. We have patched the issue in GitHub commit e0b6e58c328059829c3eb968136f17aa72b6c876. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37649 | TensorFlow is an end-to-end open source platform for machine learning. The code for `tf.raw_ops.UncompressElement` can be made to trigger a null pointer dereference. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a `CompressedElement` from a `Variant` tensor and then proceeds to dereference it for decompressing. There is no check that the `Variant` tensor contained a `CompressedElement`, so the pointer is actually `nullptr`. We have patched the issue in GitHub commit 7bdf50bb4f5c54a4997c379092888546c97c3ebd. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37648 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the code for `tf.raw_ops.SaveV2` does not properly validate the inputs and an attacker can trigger a null pointer dereference. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses `ValidateInputs` to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above. However, the validation uses `OP_REQUIRES` which translates to setting the `Status` object of the current `OpKernelContext` to an error status, followed by an empty `return` statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the next line in `Compute` that follows the call to `ValidateInputs`. This is equivalent to lacking the validation. We have patched the issue in GitHub commit 9728c60e136912a12d99ca56e106b7cce7af5986. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37647 | TensorFlow is an end-to-end open source platform for machine learning. When a user does not supply arguments that determine a valid sparse tensor, `tf.raw_ops.SparseTensorSliceDataset` implementation can be made to dereference a null pointer. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either `indices` or `values` are provided for an empty sparse tensor when the other is not. If `indices` is empty, then [code that performs validation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference. If `indices` as provided by the user is empty, then `indices` in the C++ code above is backed by an empty `std::vector`, hence calling `indices->dim_size(0)` results in null pointer dereferencing (same as calling `std::vector::at()` on an empty vector). We have patched the issue in GitHub commit 02cc160e29d20631de3859c6653184e3f876b9d7. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37646 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.StringNGrams` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls `reserve` on a `tstring` with a value that sometimes can be negative if user supplies negative `ngram_widths`. The `reserve` method calls `TF_TString_Reserve` which has an `unsigned long` argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. We have patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37645 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.QuantizeAndDequantizeV4Grad` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L126) uses the `axis` value as the size argument to `absl::InlinedVector` constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer. We have patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, and TensorFlow 2.4.3, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37644 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions providing a negative element to `num_elements` list argument of `tf.raw_ops.TensorListReserve` causes the runtime to abort the process due to reallocating a `std::vector` to have a negative number of elements. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/list_kernels.cc#L312) calls `std::vector.resize()` with the new size controlled by input given by the user, without checking that this input is valid. We have patched the issue in GitHub commit 8a6e874437670045e6c7dc6154c7412b4a2135e2. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37643 | TensorFlow is an end-to-end open source platform for machine learning. If a user does not provide a valid padding value to `tf.raw_ops.MatrixDiagPartOp`, then the code triggers a null pointer dereference (if input is empty) or produces invalid behavior, ignoring all values after the first. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L89) reads the first value from a tensor buffer without first checking that the tensor has values to read from. We have patched the issue in GitHub commit 482da92095c4d48f8784b1f00dda4f81c28d2988. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37642 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.ResourceScatterDiv` is vulnerable to a division by 0 error. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/resource_variable_ops.cc#L865) uses a common class for all binary operations but fails to treat the division by 0 case separately. We have patched the issue in GitHub commit 4aacb30888638da75023e6601149415b39763d76. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37641 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions if the arguments to `tf.raw_ops.RaggedGather` don't determine a valid ragged tensor code can trigger a read from outside of bounds of heap allocated buffers. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/ragged_gather_op.cc#L70) directly reads the first dimension of a tensor shape before checking that said tensor has rank of at least 1 (i.e., it is not a scalar). Furthermore, the implementation does not check that the list given by `params_nested_splits` is not an empty list of tensors. We have patched the issue in GitHub commit a2b743f6017d7b97af1fe49087ae15f0ac634373. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37640 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.SparseReshape` can be made to trigger an integral division by 0 exception. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements. The [reshape functor](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0. We have patched the issue in GitHub commit 4923de56ec94fff7770df259ab7f2288a74feb41. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1 as this is the other affected version. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37639 | TensorFlow is an end-to-end open source platform for machine learning. When restoring tensors via raw APIs, if the tensor name is not provided, TensorFlow can be tricked into dereferencing a null pointer. Alternatively, attackers can read memory outside the bounds of heap allocated data by providing some tensor names but not enough for a successful restoration. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/save_restore_tensor.cc#L158-L159) retrieves the tensor list corresponding to the `tensor_name` user controlled input and immediately retrieves the tensor at the restoration index (controlled via `preferred_shard` argument). This occurs without validating that the provided list has enough values. If the list is empty this results in dereferencing a null pointer (undefined behavior). If, however, the list has some elements, if the restoration index is outside the bounds this results in heap OOB read. We have patched the issue in GitHub commit 9e82dce6e6bd1f36a57e08fa85af213e2b2f2622. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37638 | TensorFlow is an end-to-end open source platform for machine learning. Sending invalid argument for `row_partition_types` of `tf.raw_ops.RaggedTensorToTensor` API results in a null pointer dereference and undefined behavior. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty. We have patched the issue in GitHub commit 301ae88b331d37a2a16159b65b255f4f9eb39314. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37637 | TensorFlow is an end-to-end open source platform for machine learning. It is possible to trigger a null pointer dereference in TensorFlow by passing an invalid input to `tf.raw_ops.CompressElement`. The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/data/compression_utils.cc#L34) was accessing the size of a buffer obtained from the return of a separate function call before validating that said buffer is valid. We have patched the issue in GitHub commit 5dc7f6981fdaf74c8c5be41f393df705841fb7c5. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37636 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.SparseDenseCwiseDiv` is vulnerable to a division by 0 error. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L56) uses a common class for all binary operations but fails to treat the division by 0 case separately. We have patched the issue in GitHub commit d9204be9f49520cdaaeb2541d1dc5187b23f31d9. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-37635 | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor. We have patched the issue in GitHub commit 87158f43f05f2720a374f3e6d22a7aaa3a33f750. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29619 | TensorFlow is an end-to-end open source platform for machine learning. Passing invalid arguments (e.g., discovered via fuzzing) to `tf.raw_ops.SparseCountSparseOutput` results in segfault. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29618 | TensorFlow is an end-to-end open source platform for machine learning. Passing a complex argument to `tf.transpose` at the same time as passing `conjugate=True` argument results in a crash. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29617 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via `CHECK`-fail in `tf.strings.substr` with invalid arguments. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29616 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of TrySimplify(https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/grappler/optimizers/arithmetic_optimizer.cc#L390-L401) has undefined behavior due to dereferencing a null pointer in corner cases that result in optimizing a node with no inputs. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29615 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `ParseAttrValue`(https://github.com/tensorflow/tensorflow/blob/c22d88d6ff33031aa113e48aa3fc9aa74ed79595/tensorflow/core/framework/attr_value_util.cc#L397-L453) can be tricked into stack overflow due to recursion by giving in a specially crafted input. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29614 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.io.decode_raw` produces incorrect results and crashes the Python interpreter when combining `fixed_length` and wider datatypes. The implementation of the padded version(https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc) is buggy due to a confusion about pointer arithmetic rules. First, the code computes(https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L61) the width of each output element by dividing the `fixed_length` value to the size of the type argument. The `fixed_length` argument is also used to determine the size needed for the output tensor(https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L63-L79). This is followed by reencoding code(https://github.com/tensorflow/tensorflow/blob/1d8903e5b167ed0432077a3db6e462daf781d1fe/tensorflow/core/kernels/decode_padded_raw_op.cc#L85-L94). The erroneous code is the last line above: it is moving the `out_data` pointer by `fixed_length * sizeof(T)` bytes whereas it only copied at most `fixed_length` bytes from the input. This results in parts of the input not being decoded into the output. Furthermore, because the pointer advance is far wider than desired, this quickly leads to writing to outside the bounds of the backing data. This OOB write leads to interpreter crash in the reproducer mentioned here, but more severe attacks can be mounted too, given that this gadget allows writing to periodically placed locations in memory. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29613 | TensorFlow is an end-to-end open source platform for machine learning. Incomplete validation in `tf.raw_ops.CTCLoss` allows an attacker to trigger an OOB read from heap. The fix will be included in TensorFlow 2.5.0. We will also cherrypick these commits 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29612 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a heap buffer overflow in Eigen implementation of `tf.raw_ops.BandedTriangularSolve`. The implementation(https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L269-L278) calls `ValidateInputTensors` for input validation but fails to validate that the two tensors are not empty. Furthermore, since `OP_REQUIRES` macro only stops execution of current function after setting `ctx->status()` to a non-OK value, callers of helper functions that use `OP_REQUIRES` must check value of `ctx->status()` before continuing. This doesn't happen in this op's implementation(https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/linalg/banded_triangular_solve_op.cc#L219), hence the validation that is present is also not effective. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29611 | TensorFlow is an end-to-end open source platform for machine learning. Incomplete validation in `SparseReshape` results in a denial of service based on a `CHECK`-failure. The implementation(https://github.com/tensorflow/tensorflow/blob/e87b51ce05c3eb172065a6ea5f48415854223285/tensorflow/core/kernels/sparse_reshape_op.cc#L40) has no validation that the input arguments specify a valid sparse tensor. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are the only affected versions. | 2.3.0, 2.3.2, 2.3.1, 2.4.1, 2.4.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-29610 | TensorFlow is an end-to-end open source platform for machine learning. The validation in `tf.raw_ops.QuantizeAndDequantizeV2` allows invalid values for `axis` argument:. The validation(https://github.com/tensorflow/tensorflow/blob/eccb7ec454e6617738554a255d77f08e60ee0808/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L74-L77) uses `||` to mix two different conditions. If `axis_ < -1` the condition in `OP_REQUIRES` will still be true, but this value of `axis_` results in heap underflow. This allows attackers to read/write to other data on the heap. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29609 | TensorFlow is an end-to-end open source platform for machine learning. Incomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_add_op.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29608 | TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in `tf.raw_ops.RaggedTensorToTensor`, an attacker can exploit an undefined behavior if input arguments are empty. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones. There are multiple `DCHECK` validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything. The fix will be included in TensorFlow 2.5.0. We will also cherrypick these commits 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29607 | TensorFlow is an end-to-end open source platform for machine learning. Incomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_sparse_binary_op_shared.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29606 | TensorFlow is an end-to-end open source platform for machine learning. A specially crafted TFLite model could trigger an OOB read on heap in the TFLite implementation of `Split_V`(https://github.com/tensorflow/tensorflow/blob/c59c37e7b2d563967da813fa50fe20b21f4da683/tensorflow/lite/kernels/split_v.cc#L99). If `axis_value` is not a value between 0 and `NumDimensions(input)`, then the `SizeOfDimension` function(https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/kernel_util.h#L148-L150) will access data outside the bounds of the tensor shape array. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29605 | TensorFlow is an end-to-end open source platform for machine learning. The TFLite code for allocating `TFLiteIntArray`s is vulnerable to an integer overflow issue(https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L24-L27). An attacker can craft a model such that the `size` multiplier is so large that the return value overflows the `int` datatype and becomes negative. In turn, this results in invalid value being given to `malloc`(https://github.com/tensorflow/tensorflow/blob/4ceffae632721e52bf3501b736e4fe9d1221cdfa/tensorflow/lite/c/common.c#L47-L52). In this case, `ret->size` would dereference an invalid pointer. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29604 | TensorFlow is an end-to-end open source platform for machine learning. The TFLite implementation of hashtable lookup is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/1a8e885b864c818198a5b2c0cbbeca5a1e833bc8/tensorflow/lite/kernels/hashtable_lookup.cc#L114-L115) An attacker can craft a model such that `values`'s first dimension would be 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29603 | TensorFlow is an end-to-end open source platform for machine learning. A specially crafted TFLite model could trigger an OOB write on heap in the TFLite implementation of `ArgMin`/`ArgMax`(https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/arg_min_max.cc#L52-L59). If `axis_value` is not a value between 0 and `NumDimensions(input)`, then the condition in the `if` is never true, so code writes past the last valid element of `output_dims->data`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29602 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `DepthwiseConv` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/1a8e885b864c818198a5b2c0cbbeca5a1e833bc8/tensorflow/lite/kernels/depthwise_conv.cc#L287-L288). An attacker can craft a model such that `input`'s fourth dimension would be 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29601 | TensorFlow is an end-to-end open source platform for machine learning. The TFLite implementation of concatenation is vulnerable to an integer overflow issue(https://github.com/tensorflow/tensorflow/blob/7b7352a724b690b11bfaae2cd54bc3907daf6285/tensorflow/lite/kernels/concatenation.cc#L70-L76). An attacker can craft a model such that the dimensions of one of the concatenation input overflow the values of `int`. TFLite uses `int` to represent tensor dimensions, whereas TF uses `int64`. Hence, valid TF models can trigger an integer overflow when converted to TFLite format. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29600 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `OneHot` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/f61c57bd425878be108ec787f4d96390579fb83e/tensorflow/lite/kernels/one_hot.cc#L68-L72). An attacker can craft a model such that at least one of the dimensions of `indices` would be 0. In turn, the `prefix_dim_size` value would become 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29599 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `Split` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/e2752089ef7ce9bcf3db0ec618ebd23ea119d0c7/tensorflow/lite/kernels/split.cc#L63-L65). An attacker can craft a model such that `num_splits` would be 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29598 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `SVDF` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/7f283ff806b2031f407db64c4d3edcda8fb9f9f5/tensorflow/lite/kernels/svdf.cc#L99-L102). An attacker can craft a model such that `params->rank` would be 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29597 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `SpaceToBatchNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/412c7d9bb8f8a762c5b266c9e73bfa165f29aac8/tensorflow/lite/kernels/space_to_batch_nd.cc#L82-L83). An attacker can craft a model such that one dimension of the `block` input is 0. Hence, the corresponding value in `block_shape` is 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29596 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `EmbeddingLookup` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/e4b29809543b250bc9b19678ec4776299dd569ba/tensorflow/lite/kernels/embedding_lookup.cc#L73-L74). An attacker can craft a model such that the first dimension of the `value` input is 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29595 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `DepthToSpace` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/depth_to_space.cc#L63-L69). An attacker can craft a model such that `params->block_size` is 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29594 | TensorFlow is an end-to-end open source platform for machine learning. TFLite's convolution code(https://github.com/tensorflow/tensorflow/blob/09c73bca7d648e961dd05898292d91a8322a9d45/tensorflow/lite/kernels/conv.cc) has multiple division where the divisor is controlled by the user and not checked to be non-zero. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29593 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of the `BatchToSpaceNd` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/b5ed552fe55895aee8bd8b191f744a069957d18d/tensorflow/lite/kernels/batch_to_space_nd.cc#L81-L82). An attacker can craft a model such that one dimension of the `block` input is 0. Hence, the corresponding value in `block_shape` is 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29592 | TensorFlow is an end-to-end open source platform for machine learning. The fix for CVE-2020-15209(https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15209) missed the case when the target shape of `Reshape` operator is given by the elements of a 1-D tensor. As such, the fix for the vulnerability(https://github.com/tensorflow/tensorflow/blob/9c1dc920d8ffb4893d6c9d27d1f039607b326743/tensorflow/lite/core/subgraph.cc#L1062-L1074) allowed passing a null-buffer-backed tensor with a 1D shape. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29591 | TensorFlow is an end-to-end open source platform for machine learning. TFlite graphs must not have loops between nodes. However, this condition was not checked and an attacker could craft models that would result in infinite loop during evaluation. In certain cases, the infinite loop would be replaced by stack overflow due to too many recursive calls. For example, the `While` implementation(https://github.com/tensorflow/tensorflow/blob/106d8f4fb89335a2c52d7c895b7a7485465ca8d9/tensorflow/lite/kernels/while.cc) could be tricked into a scneario where both the body and the loop subgraphs are the same. Evaluating one of the subgraphs means calling the `Eval` function for the other and this quickly exhaust all stack space. 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. Please consult our security guide(https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29590 | TensorFlow is an end-to-end open source platform for machine learning. The implementations of the `Minimum` and `Maximum` TFLite operators can be used to read data outside of bounds of heap allocated objects, if any of the two input tensor arguments are empty. This is because the broadcasting implementation(https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/maximum_minimum.h#L52-L56) indexes in both tensors with the same index but does not validate that the index is within bounds. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29589 | TensorFlow is an end-to-end open source platform for machine learning. The reference implementation of the `GatherNd` TFLite operator is vulnerable to a division by zero error(https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/reference_ops.h#L966). An attacker can craft a model such that `params` input would be an empty tensor. In turn, `params_shape.Dims(.)` would be zero, in at least one dimension. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29588 | TensorFlow is an end-to-end open source platform for machine learning. The optimized implementation of the `TransposeConv` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L5221-L5222). An attacker can craft a model such that `stride_{h,w}` values are 0. Code calling this function must validate these arguments. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29587 | TensorFlow is an end-to-end open source platform for machine learning. The `Prepare` step of the `SpaceToDepth` TFLite operator does not check for 0 before division(https://github.com/tensorflow/tensorflow/blob/5f7975d09eac0f10ed8a17dbb6f5964977725adc/tensorflow/lite/kernels/space_to_depth.cc#L63-L67). An attacker can craft a model such that `params->block_size` would be zero. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29586 | TensorFlow is an end-to-end open source platform for machine learning. Optimized pooling implementations in TFLite fail to check that the stride arguments are not 0 before calling `ComputePaddingHeightWidth`(https://github.com/tensorflow/tensorflow/blob/3f24ccd932546416ec906a02ddd183b48a1d2c83/tensorflow/lite/kernels/pooling.cc#L90). Since users can craft special models which will have `params->stride_{height,width}` be zero, this will result in a division by zero. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29585 | TensorFlow is an end-to-end open source platform for machine learning. The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29584 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in caused by an integer overflow in constructing a new tensor shape. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/0908c2f2397c099338b901b067f6495a5b96760b/tensorflow/core/kernels/sparse_split_op.cc#L66-L70) builds a dense shape without checking that the dimensions would not result in overflow. The `TensorShape` constructor(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when `InitDims`(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29583 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.FusedBatchNorm` is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that `scale`, `offset`, `mean` and `variance` (the last two only when required) all have the same number of elements as the number of channels of `x`. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29582 | TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in `tf.raw_ops.Dequantize`, an attacker can trigger a read from outside of bounds of heap allocated data. The implementation(https://github.com/tensorflow/tensorflow/blob/26003593aa94b1742f34dc22ce88a1e17776a67d/tensorflow/core/kernels/dequantize_op.cc#L106-L131) accesses the `min_range` and `max_range` tensors in parallel but fails to check that they have the same shape. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29581 | TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in `tf.raw_ops.CTCBeamSearchDecoder`, an attacker can trigger denial of service via segmentation faults. The implementation(https://github.com/tensorflow/tensorflow/blob/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7/tensorflow/core/kernels/ctc_decoder_ops.cc#L68-L79) fails to detect cases when the input tensor is empty and proceeds to read data from a null buffer. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29580 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.FractionalMaxPoolGrad` triggers an undefined behavior if one of the input tensors is empty. The code is also vulnerable to a denial of service attack as a `CHECK` condition becomes false and aborts the process. The implementation(https://github.com/tensorflow/tensorflow/blob/169054888d50ce488dfde9ca55d91d6325efbd5b/tensorflow/core/kernels/fractional_max_pool_op.cc#L215) fails to validate that input and output tensors are not empty and are of the same rank. Each of these unchecked assumptions is responsible for the above issues. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29579 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGrad` is vulnerable to a heap buffer overflow. The implementation(https://github.com/tensorflow/tensorflow/blob/ab1e644b48c82cb71493f4362b4dd38f4577a1cf/tensorflow/core/kernels/maxpooling_op.cc#L194-L203) fails to validate that indices used to access elements of input/output arrays are valid. Whereas accesses to `input_backprop_flat` are guarded by `FastBoundsCheck`, the indexing in `out_backprop_flat` can result in OOB access. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29578 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.FractionalAvgPoolGrad` is vulnerable to a heap buffer overflow. The implementation(https://github.com/tensorflow/tensorflow/blob/dcba796a28364d6d7f003f6fe733d82726dda713/tensorflow/core/kernels/fractional_avg_pool_op.cc#L216) fails to validate that the pooling sequence arguments have enough elements as required by the `out_backprop` tensor shape. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29577 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.AvgPool3DGrad` is vulnerable to a heap buffer overflow. The implementation(https://github.com/tensorflow/tensorflow/blob/d80ffba9702dc19d1fac74fc4b766b3fa1ee976b/tensorflow/core/kernels/pooling_ops_3d.cc#L376-L450) assumes that the `orig_input_shape` and `grad` tensors have similar first and last dimensions but does not check that this assumption is validated. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29576 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPool3DGradGrad` is vulnerable to a heap buffer overflow. The implementation(https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L694-L696) does not check that the initialization of `Pool3dParameters` completes successfully. Since the constructor(https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L48-L88) uses `OP_REQUIRES` to validate conditions, the first assertion that fails interrupts the initialization of `params`, making it contain invalid data. In turn, this might cause a heap buffer overflow, depending on default initialized values. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29575 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.ReverseSequence` allows for stack overflow and/or `CHECK`-fail based denial of service. The implementation(https://github.com/tensorflow/tensorflow/blob/5b3b071975e01f0d250c928b2a8f901cd53b90a7/tensorflow/core/kernels/reverse_sequence_op.cc#L114-L118) fails to validate that `seq_dim` and `batch_dim` arguments are valid. Negative values for `seq_dim` can result in stack overflow or `CHECK`-failure, depending on the version of Eigen code used to implement the operation. Similar behavior can be exhibited by invalid values of `batch_dim`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29574 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPool3DGradGrad` exhibits undefined behavior by dereferencing null pointers backing attacker-supplied empty tensors. The implementation(https://github.com/tensorflow/tensorflow/blob/72fe792967e7fd25234342068806707bbc116618/tensorflow/core/kernels/pooling_ops_3d.cc#L679-L703) fails to validate that the 3 tensor inputs are not empty. If any of them is empty, then accessing the elements in the tensor results in dereferencing a null pointer. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29573 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` is vulnerable to a division by 0. The implementation(https://github.com/tensorflow/tensorflow/blob/279bab6efa22752a2827621b7edb56a730233bd8/tensorflow/core/kernels/maxpooling_op.cc#L1033-L1034) fails to validate that the batch dimension of the tensor is non-zero, before dividing by this quantity. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29572 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.SdcaOptimizer` triggers undefined behavior due to dereferencing a null pointer. The implementation(https://github.com/tensorflow/tensorflow/blob/60a45c8b6192a4699f2e2709a2645a751d435cc3/tensorflow/core/kernels/sdca_internal.cc) does not validate that the user supplied arguments satisfy all constraints expected by the op(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SdcaOptimizer). 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29571 | 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/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of `boxes` input is 4, as required by [the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in `boxes` is less than 4, accesses similar to `tboxes(b, bb, 3)` will access data outside of bounds. Further during code execution there are also writes to these indices. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29570 | 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29569 | 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/ac328eaa3870491ababc147822cd04e91a790643/tensorflow/core/kernels/requantization_range_op.cc#L49-L50) assumes that the `input_min` and `input_max` tensors have at least one element, as it accesses the first element in two arrays. If the tensors are empty, `.flat<T>()` is an empty object, backed by an empty array. Hence, accesing even the 0th element is a read outside the bounds. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29568 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger undefined behavior by binding to null pointer in `tf.raw_ops.ParameterizedTruncatedNormal`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3f6fe4dfef6f57e768260b48166c27d148f3015f/tensorflow/core/kernels/parameterized_truncated_normal_op.cc#L630) does not validate input arguments before accessing the first element of `shape`. If `shape` argument is empty, then `shape_tensor.flat<T>()` is an empty array. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29567 | TensorFlow is an end-to-end open source platform for machine learning. Due to lack of validation in `tf.raw_ops.SparseDenseCwiseMul`, an attacker can trigger denial of service via `CHECK`-fails or accesses to outside the bounds of heap allocated data. Since the implementation(https://github.com/tensorflow/tensorflow/blob/38178a2f7a681a7835bb0912702a134bfe3b4d84/tensorflow/core/kernels/sparse_dense_binary_op_shared.cc#L68-L80) only validates the rank of the input arguments but no constraints between dimensions(https://www.tensorflow.org/api_docs/python/tf/raw_ops/SparseDenseCwiseMul), an attacker can abuse them to trigger internal `CHECK` assertions (and cause program termination, denial of service) or to write to memory outside of bounds of heap allocated tensor buffers. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29566 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to `tf.raw_ops.Dilation2DBackpropInput`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array. The values for `h_out` and `w_out` are guaranteed to be in range for `out_backprop` (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating `h_in_max`/`w_in_max` and `in_backprop`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29565 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.SparseFillEmptyRows`. This is because of missing validation(https://github.com/tensorflow/tensorflow/blob/fdc82089d206e281c628a93771336bf87863d5e8/tensorflow/core/kernels/sparse_fill_empty_rows_op.cc#L230-L231) that was covered under a `TODO`. If the `dense_shape` tensor is empty, then `dense_shape_t.vec<>()` would cause a null pointer dereference in the implementation of the op. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29564 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a null pointer dereference in the implementation of `tf.raw_ops.EditDistance`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/79865b542f9ffdc9caeb255631f7c56f1d4b6517/tensorflow/core/kernels/edit_distance_op.cc#L103-L159) has incomplete validation of the input parameters. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29563 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`. Eigen code operating on an empty matrix can trigger on an assertion and will cause program termination. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29562 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.IRFFT`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29561 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from `tf.raw_ops.LoadAndRemapMatrix`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) assumes that the `ckpt_path` is always a valid scalar. However, an attacker can send any other tensor as the first argument of `LoadAndRemapMatrix`. This would cause the rank `CHECK` in `scalar<T>()()` to trigger and terminate the process. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29560 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow in `tf.raw_ops.RaggedTensorToTensor`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/d94227d43aa125ad8b54115c03cece54f6a1977b/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L219-L222) uses the same index to access two arrays in parallel. Since the user controls the shape of the input arguments, an attacker could trigger a heap OOB access when `parent_output_index` is shorter than `row_split`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29559 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can access data outside of bounds of heap allocated array in `tf.raw_ops.UnicodeEncode`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/472c1f12ad9063405737679d4f6bd43094e1d36d/tensorflow/core/kernels/unicode_ops.cc) assumes that the `input_value`/`input_splits` pair specify a valid sparse tensor. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29558 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29557 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.SparseMatMul`. The division by 0 occurs deep in Eigen code because the `b` tensor is empty. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29556 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.Reverse`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/36229ea9e9451dac14a8b1f4711c435a1d84a594/tensorflow/core/kernels/reverse_op.cc#L75-L76) performs a division based on the first dimension of the tensor argument. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29555 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.FusedBatchNorm`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/828f346274841fa7505f7020e88ca36c22e557ab/tensorflow/core/kernels/fused_batch_norm_op.cc#L295-L297) performs a division based on the last dimension of the `x` tensor. Since this is controlled by the user, an attacker can trigger a denial of service. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29554 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.DenseCountSparseOutput`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/efff014f3b2d8ef6141da30c806faf141297eca1/tensorflow/core/kernels/count_ops.cc#L123-L127) computes a divisor value from user data but does not check that the result is 0 before doing the division. Since `data` is given by the `values` argument, `num_batch_elements` is 0. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, and TensorFlow 2.3.3, as these are also affected. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29553 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can read data outside of bounds of heap allocated buffer in `tf.raw_ops.QuantizeAndDequantizeV3`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/11ff7f80667e6490d7b5174aa6bf5e01886e770f/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L237) does not validate the value of user supplied `axis` attribute before using it to index in the array backing the `input` argument. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29552 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service by controlling the values of `num_segments` tensor argument for `UnsortedSegmentJoin`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a2a607db15c7cd01d754d37e5448d72a13491bdb/tensorflow/core/kernels/unsorted_segment_join_op.cc#L92-L93) assumes that the `num_segments` tensor is a valid scalar. Since the tensor is empty the `CHECK` involved in `.scalar<T>()()` that checks that the number of elements is exactly 1 will be invalidated and this would result in process termination. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29551 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `MatrixTriangularSolve`(https://github.com/tensorflow/tensorflow/blob/8cae746d8449c7dda5298327353d68613f16e798/tensorflow/core/kernels/linalg/matrix_triangular_solve_op_impl.h#L160-L240) fails to terminate kernel execution if one validation condition fails. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29550 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values. The user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger. Later, these computed values are used as arguments(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to `GeneratePoolingSequence`(https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation. Since `output_length` can be 0, this results in runtime crashing. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29549 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero. Since `vector_num_elements` is determined based on input shapes(https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 0. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29548 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc) does not validate all constraints specified in the op's contract(https://www.tensorflow.org/api_docs/python/tf/raw_ops/QuantizedBatchNormWithGlobalNormalization). 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29547 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a segfault and denial of service via accessing data outside of bounds in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty. If any of these inputs is empty, `.flat<T>()` is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29546 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger an integer division by zero undefined behavior in `tf.raw_ops.QuantizedBiasAdd`. This is because the implementation of the Eigen kernel(https://github.com/tensorflow/tensorflow/blob/61bca8bd5ba8a68b2d97435ddfafcdf2b85672cd/tensorflow/core/kernels/quantization_utils.h#L812-L849) does a division by the number of elements of the smaller input (based on shape) without checking that this is not zero. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29545 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in converting sparse tensors to CSR Sparse matrices. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap. If the value at `indices(i, 0)` is such that `indices(i, 0) + 1` is outside the bounds of `csr_row_ptr`, this results in writing outside of bounds of heap allocated data. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29544 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.QuantizeAndDequantizeV4Grad`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the `input_*` tensors. In turn, this results in the tensors being passes as they are to `QuantizeAndDequantizePerChannelGradientImpl`(https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306). However, the `vec<T>` method, requires the rank to 1 and triggers a `CHECK` failure otherwise. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 as this is the only other affected version. | 2.4.1, 2.4.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-29543 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29542 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow by passing crafted inputs to `tf.raw_ops.StringNGrams`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L171-L185) fails to consider corner cases where input would be split in such a way that the generated tokens should only contain padding elements. If input is such that `num_tokens` is 0, then, for `data_start_index=0` (when left padding is present), the marked line would result in reading `data[-1]`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29541 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a dereference of a null pointer in `tf.raw_ops.StringNGrams`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L67-L74) does not fully validate the `data_splits` argument. This would result in `ngrams_data`(https://github.com/tensorflow/tensorflow/blob/1cdd4da14282210cc759e468d9781741ac7d01bf/tensorflow/core/kernels/string_ngrams_op.cc#L106-L110) to be a null pointer when the output would be computed to have 0 or negative size. Later writes to the output tensor would then cause a null pointer dereference. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29540 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow to occur in `Conv2DBackpropFilter`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L495-L497) computes the size of the filter tensor but does not validate that it matches the number of elements in `filter_sizes`. Later, when reading/writing to this buffer, code uses the value computed here, instead of the number of elements in the tensor. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29539 | TensorFlow is an end-to-end open source platform for machine learning. Calling `tf.raw_ops.ImmutableConst`(https://www.tensorflow.org/api_docs/python/tf/raw_ops/ImmutableConst) with a `dtype` of `tf.resource` or `tf.variant` results in a segfault in the implementation as code assumes that the tensor contents are pure scalars. We have patched the issue in 4f663d4b8f0bec1b48da6fa091a7d29609980fa4 and will release TensorFlow 2.5.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. If using `tf.raw_ops.ImmutableConst` in code, you can prevent the segfault by inserting a filter for the `dtype` argument. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29538 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a division by zero to occur in `Conv2DBackpropFilter`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments). If all shapes are empty then `work_unit_size` is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29537 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow in `QuantizedResizeBilinear` by passing in invalid thresholds for the quantization. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/50711818d2e61ccce012591eeb4fdf93a8496726/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L705-L706) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29536 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow in `QuantizedReshape` by passing in invalid thresholds for the quantization. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a324ac84e573fba362a5e53d4e74d5de6729933e/tensorflow/core/kernels/quantized_reshape_op.cc#L38-L55) assumes that the 2 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29535 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow in `QuantizedMul` by passing in invalid thresholds for the quantization. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/87cf4d3ea9949051e50ca3f071fc909538a51cd0/tensorflow/core/kernels/quantized_mul_op.cc#L287-L290) assumes that the 4 arguments are always valid scalars and tries to access the numeric value directly. However, if any of these tensors is empty, then `.flat<T>()` is an empty buffer and accessing the element at position 0 results in overflow. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29534 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.SparseConcat`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/b432a38fe0e1b4b904a6c222cbce794c39703e87/tensorflow/core/kernels/sparse_concat_op.cc#L76) takes the values specified in `shapes[0]` as dimensions for the output shape. The `TensorShape` constructor(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when `InitDims`(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29533 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK` failure by passing an empty image to `tf.raw_ops.DrawBoundingBoxes`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses `CHECK_*` assertions instead of `OP_REQUIRES` to validate user controlled inputs. Whereas `OP_REQUIRES` allows returning an error condition back to the user, the `CHECK_*` macros result in a crash if the condition is false, similar to `assert`. In this case, `height` is 0 from the `images` input. This results in `max_box_row_clamp` being negative and the assertion being falsified, followed by aborting program execution. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29532 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can force accesses outside the bounds of heap allocated arrays by passing in invalid tensor values to `tf.raw_ops.RaggedCross`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/efea03b38fb8d3b81762237dc85e579cc5fc6e87/tensorflow/core/kernels/ragged_cross_op.cc#L456-L487) lacks validation for the user supplied arguments. Each of the above branches call a helper function after accessing array elements via a `*_list[next_*]` pattern, followed by incrementing the `next_*` index. However, as there is no validation that the `next_*` values are in the valid range for the corresponding `*_list` arrays, this results in heap OOB reads. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29531 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a `CHECK` fail in PNG encoding by providing an empty input tensor as the pixel data. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/kernels/image/encode_png_op.cc#L57-L60) only validates that the total number of pixels in the image does not overflow. Thus, an attacker can send an empty matrix for encoding. However, if the tensor is empty, then the associated buffer is `nullptr`. Hence, when calling `png::WriteImageToBuffer`(https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/kernels/image/encode_png_op.cc#L79-L93), the first argument (i.e., `image.flat<T>().data()`) is `NULL`. This then triggers the `CHECK_NOTNULL` in the first line of `png::WriteImageToBuffer`(https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/lib/png/png_io.cc#L345-L349). Since `image` is null, this results in `abort` being called after printing the stacktrace. Effectively, this allows an attacker to mount a denial of service attack. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29530 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a null pointer dereference by providing an invalid `permutation` to `tf.raw_ops.SparseMatrixSparseCholesky`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/kernels/sparse/sparse_cholesky_op.cc#L85-L86) fails to properly validate the input arguments. Although `ValidateInputs` is called and there are checks in the body of this function, the code proceeds to the next line in `ValidateInputs` since `OP_REQUIRES`(https://github.com/tensorflow/tensorflow/blob/080f1d9e257589f78b3ffb75debf584168aa6062/tensorflow/core/framework/op_requires.h#L41-L48) is a macro that only exits the current function. Thus, the first validation condition that fails in `ValidateInputs` will cause an early return from that function. However, the caller will continue execution from the next line. The fix is to either explicitly check `context->status()` or to convert `ValidateInputs` to return a `Status`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29529 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a heap buffer overflow in `tf.raw_ops.QuantizedResizeBilinear` by manipulating input values so that float rounding results in off-by-one error in accessing image elements. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L62-L66) computes two integers (representing the upper and lower bounds for interpolation) by ceiling and flooring a floating point value. For some values of `in`, `interpolation->upper[i]` might be smaller than `interpolation->lower[i]`. This is an issue if `interpolation->upper[i]` is capped at `in_size-1` as it means that `interpolation->lower[i]` points outside of the image. Then, in the interpolation code(https://github.com/tensorflow/tensorflow/blob/44b7f486c0143f68b56c34e2d01e146ee445134a/tensorflow/core/kernels/quantized_resize_bilinear_op.cc#L245-L264), this would result in heap buffer overflow. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29528 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a division by 0 in `tf.raw_ops.QuantizedMul`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/55900e961ed4a23b438392024912154a2c2f5e85/tensorflow/core/kernels/quantized_mul_op.cc#L188-L198) does a division by a quantity that is controlled by the caller. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29527 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a division by 0 in `tf.raw_ops.QuantizedConv2D`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/00e9a4d67d76703fa1aee33dac582acf317e0e81/tensorflow/core/kernels/quantized_conv_ops.cc#L257-L259) does a division by a quantity that is controlled by the caller. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29526 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a division by 0 in `tf.raw_ops.Conv2D`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/988087bd83f144af14087fe4fecee2d250d93737/tensorflow/core/kernels/conv_ops.cc#L261-L263) does a division by a quantity that is controlled by the caller. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29525 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropInput`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/b40060c9f697b044e3107917c797ba052f4506ab/tensorflow/core/kernels/conv_grad_input_ops.h#L625-L655) does a division by a quantity that is controlled by the caller. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29524 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropFilter`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/496c2630e51c1a478f095b084329acedb253db6b/tensorflow/core/kernels/conv_grad_shape_utils.cc#L130) does a modulus operation where the divisor is controlled by the caller. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29523 | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.AddManySparseToTensorsMap`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/kernels/sparse_tensors_map_ops.cc#L257) takes the values specified in `sparse_shape` as dimensions for the output shape. The `TensorShape` constructor(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when `InitDims`(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29522 | TensorFlow is an end-to-end open source platform for machine learning. The `tf.raw_ops.Conv3DBackprop*` operations fail to validate that the input tensors are not empty. In turn, this would result in a division by 0. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/a91bb59769f19146d5a0c20060244378e878f140/tensorflow/core/kernels/conv_grad_ops_3d.cc#L430-L450) does not check that the divisor used in computing the shard size is not zero. Thus, if attacker controls the input sizes, they can trigger a denial of service via a division by zero error. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29521 | TensorFlow is an end-to-end open source platform for machine learning. Specifying a negative dense shape in `tf.raw_ops.SparseCountSparseOutput` results in a segmentation fault being thrown out from the standard library as `std::vector` invariants are broken. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/8f7b60ee8c0206a2c99802e3a4d1bb55d2bc0624/tensorflow/core/kernels/count_ops.cc#L199-L213) assumes the first element of the dense shape is always positive and uses it to initialize a `BatchedMap<T>` (i.e., `std::vector<absl::flat_hash_map<int64,T>>`(https://github.com/tensorflow/tensorflow/blob/8f7b60ee8c0206a2c99802e3a4d1bb55d2bc0624/tensorflow/core/kernels/count_ops.cc#L27)) data structure. If the `shape` tensor has more than one element, `num_batches` is the first value in `shape`. Ensuring that the `dense_shape` argument is a valid tensor shape (that is, all elements are non-negative) solves this issue. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3. | 2.3.0, 2.3.2, 2.3.1, 2.4.1, 2.4.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-29520 | TensorFlow is an end-to-end open source platform for machine learning. Missing validation between arguments to `tf.raw_ops.Conv3DBackprop*` operations can result in heap buffer overflows. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/4814fafb0ca6b5ab58a09411523b2193fed23fed/tensorflow/core/kernels/conv_grad_shape_utils.cc#L94-L153) assumes that the `input`, `filter_sizes` and `out_backprop` tensors have the same shape, as they are accessed in parallel. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29519 | TensorFlow is an end-to-end open source platform for machine learning. The API of `tf.raw_ops.SparseCross` allows combinations which would result in a `CHECK`-failure and denial of service. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3d782b7d47b1bf2ed32bd4a246d6d6cadc4c903d/tensorflow/core/kernels/sparse_cross_op.cc#L114-L116) is tricked to consider a tensor of type `tstring` which in fact contains integral elements. Fixing the type confusion by preventing mixing `DT_STRING` and `DT_INT64` types solves this issue. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29518 | TensorFlow is an end-to-end open source platform for machine learning. In eager mode (default in TF 2.0 and later), session operations are invalid. However, users could still call the raw ops associated with them and trigger a null pointer dereference. The implementation(https://github.com/tensorflow/tensorflow/blob/eebb96c2830d48597d055d247c0e9aebaea94cd5/tensorflow/core/kernels/session_ops.cc#L104) dereferences the session state pointer without checking if it is valid. Thus, in eager mode, `ctx->session_state()` is nullptr and the call of the member function is undefined behavior. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29517 | TensorFlow is an end-to-end open source platform for machine learning. A malicious user could trigger a division by 0 in `Conv3D` implementation. The implementation(https://github.com/tensorflow/tensorflow/blob/42033603003965bffac51ae171b51801565e002d/tensorflow/core/kernels/conv_ops_3d.cc#L143-L145) does a modulo operation based on user controlled input. Thus, when `filter` has a 0 as the fifth element, this results in a division by 0. Additionally, if the shape of the two tensors is not valid, an Eigen assertion can be triggered, resulting in a program crash. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29516 | TensorFlow is an end-to-end open source platform for machine learning. Calling `tf.raw_ops.RaggedTensorToVariant` with arguments specifying an invalid ragged tensor results in a null pointer dereference. The implementation of `RaggedTensorToVariant` operations(https://github.com/tensorflow/tensorflow/blob/904b3926ed1c6c70380d5313d282d248a776baa1/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L39-L40) does not validate that the ragged tensor argument is non-empty. Since `batched_ragged` contains no elements, `batched_ragged.splits` is a null vector, thus `batched_ragged.splits(0)` will result in dereferencing `nullptr`. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29515 | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `MatrixDiag*` operations(https://github.com/tensorflow/tensorflow/blob/4c4f420e68f1cfaf8f4b6e8e3eb857e9e4c3ff33/tensorflow/core/kernels/linalg/matrix_diag_op.cc#L195-L197) does not validate that the tensor arguments are non-empty. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29514 | TensorFlow is an end-to-end open source platform for machine learning. If the `splits` argument of `RaggedBincount` does not specify a valid `SparseTensor`(https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the `splits` tensor buffer in the implementation of the `RaggedBincount` op(https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L446). Before the `for` loop, `batch_idx` is set to 0. The attacker sets `splits(0)` to be 7, hence the `while` loop does not execute and `batch_idx` remains 0. This then results in writing to `out(-1, bin)`, which is before the heap allocated buffer for the output tensor. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are also affected. | 2.3.0, 2.3.2, 2.3.1, 2.4.1, 2.4.0 | Patch → NO_SAFE_VERSION |
| CVE-2021-29513 | TensorFlow is an end-to-end open source platform for machine learning. Calling TF operations with tensors of non-numeric types when the operations expect numeric tensors result in null pointer dereferences. The conversion from Python array to C++ array(https://github.com/tensorflow/tensorflow/blob/ff70c47a396ef1e3cb73c90513da4f5cb71bebba/tensorflow/python/lib/core/ndarray_tensor.cc#L113-L169) is vulnerable to a type confusion. 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2021-29512 | TensorFlow is an end-to-end open source platform for machine learning. If the `splits` argument of `RaggedBincount` does not specify a valid `SparseTensor`(https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the `splits` tensor buffer in the implementation of the `RaggedBincount` op(https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433). Before the `for` loop, `batch_idx` is set to 0. The user controls the `splits` array, making it contain only one element, 0. Thus, the code in the `while` loop would increment `batch_idx` and then try to read `splits(1)`, which is outside of bounds. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are also affected. | 2.3.0, 2.3.2, 2.3.1, 2.4.1, 2.4.0 | Patch → NO_SAFE_VERSION |
| CVE-2020-5215 | In TensorFlow before 1.15.2 and 2.0.1, converting a string (from Python) to a tf.float16 value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode. This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a tf.float16 value. Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar tf.float16 value with a scalar string will trigger this issue due to automatic conversions. This can be easily reproduced by tf.constant("hello", tf.float16), if eager execution is enabled. This issue is patched in TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched. TensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected. Users are encouraged to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-26271 | In affected versions of TensorFlow under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The MakeEdge function creates an edge between one output tensor of the src node (given by output_index) and the input slot of the dst node (given by input_index). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding DataType values and comparing these for equality. However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-26270 | In affected versions of TensorFlow running an LSTM/GRU model where the LSTM/GRU layer receives an input with zero-length results in a CHECK failure when using the CUDA backend. This can result in a query-of-death vulnerability, via denial of service, if users can control the input to the layer. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-26268 | In affected versions of TensorFlow the tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area. If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault. This is because the allocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overridden. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-26267 | In affected versions of TensorFlow the tf.raw_ops.DataFormatVecPermute API does not validate the src_format and dst_format attributes. The code assumes that these two arguments define a permutation of NHWC. This can result in uninitialized memory accesses, read outside of bounds and even crashes. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-26266 | In affected versions of TensorFlow under certain cases a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to default initialize the quantized floating point types in Eigen. This is fixed in versions 1.15.5, 2.0.4, 2.1.3, 2.2.2, 2.3.2, and 2.4.0. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15266 | In Tensorflow before version 2.4.0, when the `boxes` argument of `tf.image.crop_and_resize` has a very large value, the CPU kernel implementation receives it as a C++ `nan` floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15265 | In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15214 | In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a write out bounds / segmentation fault if the segment ids are not sorted. Code assumes that the segment ids are in increasing order, using the last element of the tensor holding them to determine the dimensionality of output tensor. This results in allocating insufficient memory for the output tensor and in a write outside the bounds of the output array. This usually results in a segmentation fault, but depending on runtime conditions it can provide for a write gadget to be used in future memory corruption-based exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are sorted, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. | 2.3.0, 2.2.0 | Patch → NO_SAFE_VERSION |
| CVE-2020-15213 | In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimensionality of output tensor, attackers can use a very large value to trigger a large allocation. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps. However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. | 2.3.0, 2.2.0 | Patch → NO_SAFE_VERSION |
| CVE-2020-15212 | In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. The issue is patched in commit 204945b19e44b57906c9344c0d00120eeeae178a and is released in TensorFlow versions 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. | 2.3.0, 2.2.0 | Patch → NO_SAFE_VERSION |
| CVE-2020-15211 | In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor. However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative `-1` value as index for these tensors. This results in special casing during validation at model loading time. Unfortunately, this means that the `-1` index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays. This results in both read and write gadgets, albeit very limited in scope. The issue is patched in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83), and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that only operators which accept optional inputs use the `-1` special value and only for the tensors that they expect to be optional. Since this allow-list type approach is erro-prone, we advise upgrading to the patched code. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15210 | In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and will release patch releases for all versions between 1.15 and 2.3. We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15209 | In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`. However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue is patched in commit 0b5662bc, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15208 | 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. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15207 | In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses `ResolveAxis` to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the `DCHECK` does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption. The issue is patched in commit 2d88f470dea2671b430884260f3626b1fe99830a, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15206 | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, changing the TensorFlow's `SavedModel` protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using `tensorflow-serving` or other inference-as-a-service installments. Fixed were added in commits f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d (both going into TensorFlow 2.2.0 and 2.3.0 but not yet backported to earlier versions). However, this was not enough, as #41097 reports a different failure mode. The issue is patched in commit adf095206f25471e864a8e63a0f1caef53a0e3a6, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15205 | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `data_splits` argument of `tf.raw_ops.StringNGrams` lacks validation. This allows a user to pass values that can cause heap overflow errors and even leak contents of memory In the linked code snippet, all the binary strings after `ee ff` are contents from the memory stack. Since these can contain return addresses, this data leak can be used to defeat ASLR. The issue is patched in commit 0462de5b544ed4731aa2fb23946ac22c01856b80, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15204 | In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling `tf.raw_ops.GetSessionHandle` or `tf.raw_ops.GetSessionHandleV2` results in a null pointer dereference In linked snippet, in eager mode, `ctx->session_state()` returns `nullptr`. Since code immediately dereferences this, we get a segmentation fault. The issue is patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15203 | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the `fill` argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed. This may result in segmentation fault. The issue is patched in commit 33be22c65d86256e6826666662e40dbdfe70ee83, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15202 | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15201 | In Tensorflow before version 2.3.1, the `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Hence, the code is prone to heap buffer overflow. If `split_values` does not end with a value at least `num_values` then the `while` loop condition will trigger a read outside of the bounds of `split_values` once `batch_idx` grows too large. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15200 | In Tensorflow before version 2.3.1, the `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Thus, the code sets up conditions to cause a heap buffer overflow. A `BatchedMap` is equivalent to a vector where each element is a hashmap. However, if the first element of `splits_values` is not 0, `batch_idx` will never be 1, hence there will be no hashmap at index 0 in `per_batch_counts`. Trying to access that in the user code results in a segmentation fault. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15199 | In Tensorflow before version 2.3.1, the `RaggedCountSparseOutput` does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the `splits` tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure. Since `BatchedMap` is equivalent to a vector, it needs to have at least one element to not be `nullptr`. If user passes a `splits` tensor that is empty or has exactly one element, we get a `SIGABRT` signal raised by the operating system. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15198 | In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15197 | In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix. However, malicious users can pass in tensors of different rank, resulting in a `CHECK` assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15196 | In Tensorflow version 2.3.0, the `SparseCountSparseOutput` and `RaggedCountSparseOutput` implementations don't validate that the `weights` tensor has the same shape as the data. The check exists for `DenseCountSparseOutput`, where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15195 | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the implementation of `SparseFillEmptyRowsGrad` uses a double indexing pattern. It is possible for `reverse_index_map(i)` to be an index outside of bounds of `grad_values`, thus resulting in a heap buffer overflow. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15194 | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1." | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15193 | In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of `dlpack.to_dlpack` can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing in a Python object instead of a tensor. The uninitialized memory address is due to a `reinterpret_cast` Since the `PyObject` is a Python object, not a TensorFlow Tensor, the cast to `EagerTensor` fails. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15192 | In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to `dlpack.to_dlpack` there is a memory leak following an expected validation failure. The issue occurs because the `status` argument during validation failures is not properly checked. Since each of the above methods can return an error status, the `status` value must be checked before continuing. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15191 | In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition. However, this `status` argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2020-15190 | In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `tf.raw_ops.Switch` operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault The issue is patched in commit da8558533d925694483d2c136a9220d6d49d843c, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2019-9635 | NULL pointer dereference in Google TensorFlow before 1.12.2 could cause a denial of service via an invalid GIF file. | 1.2.1, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.10.0, 1.8.0, 1.2.0 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2019-16778 | In TensorFlow before 1.15, a heap buffer overflow in UnsortedSegmentSum can be produced when the Index template argument is int32. In this case data_size and num_segments fields are truncated from int64 to int32 and can produce negative numbers, resulting in accessing out of bounds heap memory. This is unlikely to be exploitable and was detected and fixed internally in TensorFlow 1.15 and 2.0. | 1.2.1, 1.14.0, 1.12.3, 1.12.0, 1.9.0, 1.4.1, 0.12.0, 1.13.2 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2018-8825 | Google TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local). | 1.5.1, 1.6.0, 1.7.0, 1.5.0 | Patch → NO_SAFE_VERSION |
| CVE-2018-7577 | Memcpy parameter overlap in Google Snappy library 1.1.4, as used in Google TensorFlow before 1.7.1, could result in a crash or read from other parts of process memory. | 1.2.1, 1.4.1, 1.2.0, 1.5.1, 1.3.0, 1.6.0, 1.4.0, 1.7.0 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2018-7576 | Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent. | 1.2.1, 1.4.1, 0.12.0, 1.2.0, 1.5.1, 1.3.0, 1.0.0, 1.6.0 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2018-7575 | Google TensorFlow 1.7.x and earlier is affected by a Buffer Overflow vulnerability. The type of exploitation is context-dependent. | 1.2.1, 1.4.1, 1.2.0, 1.5.1, 1.3.0, 1.0.0, 1.6.0, 1.4.0 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2018-21233 | TensorFlow before 1.7.0 has an integer overflow that causes an out-of-bounds read, possibly causing disclosure of the contents of process memory. This occurs in the DecodeBmp feature of the BMP decoder in core/kernels/decode_bmp_op.cc. | 1.2.1, 1.4.1, 0.12.0, 1.2.0, 1.5.1, 1.3.0, 1.0.0, 1.6.0 (Show all) | Patch → NO_SAFE_VERSION |
| CVE-2018-10055 | Invalid memory access and/or a heap buffer overflow in the TensorFlow XLA compiler in Google TensorFlow before 1.7.1 could cause a crash or read from other parts of process memory via a crafted configuration file. | 1.2.1, 1.4.1, 1.2.0, 1.5.1, 1.3.0, 1.6.0, 1.4.0, 1.7.0 (Show all) | Patch → NO_SAFE_VERSION |
Instantly see if these tensorflow-gpu vulnerabilities affect your code.