CVE-2024-12886

An Out-Of-Memory (OOM) vulnerability exists in the `ollama` server version 0.3.14. This vulnerability can be triggered when a malicious API server responds with a gzip bomb HTTP response, leading to the `ollama` server crashing. The vulnerability is present in the `makeRequestWithRetry` and `getAuthorizationToken` functions, which use `io.ReadAll` to read the response body. This can result in excessive memory usage and a Denial of Service (DoS) condition.

An Out-Of-Memory (OOM) vulnerability exists in the `ollama` server version 0.3.14. This vulnerability can be triggered when a malicious API server responds with a gzip bomb HTTP response, leading to the `ollama` server crashing. The vulnerability is present in the `makeRequestWithRetry` and `getAuthorizationToken` functions, which use `io.ReadAll` to read the response body. This can result in excessive memory usage and a Denial of Service (DoS) condition.

Ollama Vulnerable to Denial of Service (DoS) via Crafted GZIP in github.com/ollama/ollama

An Out-Of-Memory (OOM) vulnerability exists in the `ollama` server version 0.3.14. This vulnerability can be triggered when a malicious API server responds with a gzip bomb HTTP response, leading to the `ollama` server crashing. The vulnerability is present in the `makeRequestWithRetry` and `getAuthorizationToken` functions, which use `io.ReadAll` to read the response body. This can result in excessive memory usage and a Denial of Service (DoS) condition.

Existe una vulnerabilidad de falta de memoria (OOM) en la versión 0.3.14 del servidor `ollama`. Esta vulnerabilidad puede activarse cuando un servidor API malicioso responde con una bomba HTTP gzip, lo que provoca el bloqueo del servidor `ollama`. La vulnerabilidad está presente en las funciones `makeRequestWithRetry` y `getAuthorizationToken`, que utilizan `io.ReadAll` para leer el cuerpo de la respuesta. Esto puede provocar un uso excesivo de memoria y una denegación de servicio (DoS).