You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This CVE record has been marked for NVD enrichment efforts.
Description
Uncontrolled Resource Consumption vulnerability in ninenines gun (gun_http module) allows a malicious server to exhaust client memory via unbounded HTTP/1.1 response buffering.
In gun_http:handle/5, three clauses accumulate incoming TCP data into the connection's buffer field using binary concatenation with no upper-bound check: the head clause appends data until the \r\n\r\n header terminator is found; the body_chunked clause appends data whenever cow_http_te:stream_chunked/2 returns a more result indicating an incomplete chunk boundary; and the body_trailer clause appends data until the trailing \r\n\r\n is found. In each case, when the expected terminator never arrives, the enlarged binary is stored back into state and the process waits for more data, with no configurable or hard-coded ceiling on buffer size.
A malicious or compromised server can exploit this by sending a partial response that never completes. For example, a response may begin with HTTP/1.1 200 OK\r\nX-Pad: followed by an unbounded stream of arbitrary bytes, never sending the header terminator. The gun connection process will continuously append the incoming data to its buffer, causing unbounded heap growth. Because BEAM imposes no per-process heap limit by default, a single malicious connection can exhaust all available memory on the node, causing a node-wide out-of-memory crash.
This issue affects gun: from 1.0.0 before 2.4.0.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: gun de ninenines, Description: Vulnerabilidad de Consumo de Recursos Incontrolado en ninenines gun (módulo gun_http) permite a un servidor malicioso agotar la memoria del cliente a través del almacenamiento en búfer de respuestas HTTP/1.1 ilimitado.
En gun_http:handle/5, tres cláusulas acumulan datos TCP entrantes en el campo de búfer de la conexión utilizando concatenación binaria sin verificación de límite superior: la cláusula 'head' añade datos hasta que se encuentra el terminador de encabezado \r\n\r\n; la cláusula 'body_chunked' añade datos cada vez que cow_http_te:stream_chunked/2 devuelve un resultado 'more' indicando un límite de fragmento incompleto; y la cláusula 'body_trailer' añade datos hasta que se encuentra el \r\n\r\n final. En cada caso, cuando el terminador esperado nunca llega, el binario ampliado se almacena de nuevo en el estado y el proceso espera más datos, sin un límite configurable o codificado rígidamente para el tamaño del búfer.
Un servidor malicioso o comprometido puede explotar esto enviando una respuesta parcial que nunca se completa. Por ejemplo, una respuesta puede comenzar con HTTP/1.1 200 OK\r\nX-Pad: seguido de un flujo ilimitado de bytes arbitrarios, sin enviar nunca el terminador de encabezado. El proceso de conexión de gun añadirá continuamente los datos entrantes a su búfer, causando un crecimiento ilimitado del 'heap'. Debido a que BEAM no impone un límite de 'heap' por proceso por defecto, una única conexión maliciosa puede agotar toda la memoria disponible en el nodo, causando un fallo por falta de memoria en todo el nodo.
Este problema afecta a gun: desde 1.0.0 antes de 2.4.0.
Uncontrolled Resource Consumption vulnerability in ninenines gun (gun_http module) allows a malicious server to exhaust client memory via unbounded HTTP/1.1 response buffering.
In gun_http:handle/5, three clauses accumulate incoming TCP data into the connection's buffer field using binary concatenation with no upper-bound check: the head clause appends data until the \r\n\r\n header terminator is found; the body_chunked clause appends data whenever cow_http_te:stream_chunked/2 returns a more result indicating an incomplete chunk boundary; and the body_trailer clause appends data until the trailing \r\n\r\n is found. In each case, when the expected terminator never arrives, the enlarged binary is stored back into state and the process waits for more data, with no configurable or hard-coded ceiling on buffer size.
A malicious or compromised server can exploit this by sending a partial response that never completes. For example, a response may begin with HTTP/1.1 200 OK\r\nX-Pad: followed by an unbounded stream of arbitrary bytes, never sending the header terminator. The gun connection process will continuously append the incoming data to its buffer, causing unbounded heap growth. Because BEAM imposes no per-process heap limit by default, a single malicious connection can exhaust all available memory on the node, causing a node-wide out-of-memory crash.
This issue affects gun: from 1.0.0 before 2.4.0.
) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
