> CVE-2020-15211 [MEDIUM]

« BACK_TO_HOME
PUBLISHED
2020-09-25 19:15
MODIFIED
2024-11-21 05:05
CVSS_SCORE V3
4.8
EPSS (Prob. Exploit)
0.92%
Top 39.2%
DATA SOURCES:
NVD 🔗 2025-10-18 CVE PROJECT 🔗 2026-01-19 FIRST EPSS 🔗 2026-11-15 GITHUB 🔗 2026-09-28

> DESCRIPTION

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.

> AFFECTED_PRODUCTS

Opensuse - Leap
Version: 15.2
Google - Tensorflow
< 1.15.4
Google - Tensorflow
>= 2.0.0 < 2.0.3
Google - Tensorflow
>= 2.1.0 < 2.1.2
Google - Tensorflow
>= 2.2.0 < 2.2.1
Google - Tensorflow
>= 2.3.0 < 2.3.1

> CVSS V3 METRICS

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

> MÉTRIQUES CVSS DÉTAILLÉES

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Métrique Valeur Interprétation
AV (Vecteur d'Attaque)
Attack Vector
Network (N)
Exploit possible à distance via réseau (HTTP, API, etc.)
AC (Complexité d'Attaque)
Attack Complexity
High (H)
Conditions spécifiques doivent être réunies pour exploiter
PR (Privilèges Requis)
Privileges Required
None (N)
Aucune authentification requise
UI (Interaction Utilisateur)
User Interaction
None (N)
Aucune interaction utilisateur nécessaire
S (Périmètre)
Scope
Unchanged (U)
Impact reste dans le périmètre du composant compromis
C (Impact Confidentialité)
Confidentiality Impact
Low (L)
Divulgation limitée d'informations
I (Impact Intégrité)
Integrity Impact
Low (L)
Modification limitée des données possible
A (Impact Disponibilité)
Availability Impact
None (N)
Aucune interruption de service

> RÉSUMÉ DES IMPACTS

Confidentialité
Low
Divulgation limitée d'informations
Intégrité
Low
Modification limitée des données possible
Disponibilité
None
Aucune interruption de service

> GITHUB SECURITY ADVISORY

GHSA-cvpc-8phh-8f45 MODERATE

Out of bounds access in tensorflow-lite

AFFECTED PACKAGES:
PIP / tensorflow-gpu
= 2.3.0
Fixed in: 2.3.1
PIP / tensorflow-gpu
= 2.2.0
Fixed in: 2.2.1
PIP / tensorflow-gpu
>= 2.1.0, < 2.1.2
Fixed in: 2.1.2
PIP / tensorflow-gpu
>= 2.0.0, < 2.0.3
Fixed in: 2.0.3
PIP / tensorflow-gpu
< 1.15.4
Fixed in: 1.15.4
PIP / tensorflow-cpu
= 2.3.0
Fixed in: 2.3.1
PIP / tensorflow-cpu
= 2.2.0
Fixed in: 2.2.1
PIP / tensorflow-cpu
>= 2.1.0, < 2.1.2
Fixed in: 2.1.2
PIP / tensorflow-cpu
>= 2.0.0, < 2.0.3
Fixed in: 2.0.3
PIP / tensorflow-cpu
< 1.15.4
Fixed in: 1.15.4

> HISTORIQUE DES MODIFICATIONS

Première apparition
25/09/2020 19:15
Source: NVD
📊 ENRICHISSEMENT 18/10/2025 14:23
CVEPROJECT
Champ modifié: CVE Project
Ancienne valeur:
Non
Nouvelle valeur:
Oui
Total des modifications: 1 Dernière mise à jour: 1 year ago
« BACK_TO_HOME