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.
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in benoitc hackney allows Excessive Allocation. The Alt-Svc response header parser in src/hackney_altsvc.erl does not guarantee forward progress. When parse_token/2 receives a non-token, non-whitespace, non-comma byte (e.g. !, @, =, ;), it returns the input unchanged. skip_comma/1 also returns the buffer unchanged when the first byte is not a comma. parse_entries/2 then recurses with identical data, creating a tight infinite tail-recursive loop that pins a scheduler at 100% CPU. The calling process never returns.
The entry point parse_and_cache/3 is called synchronously in the connection process on every HTTP response. A single-byte Alt-Svc: ! response header is sufficient to trigger the hang; the header is fully controlled by any HTTP origin the client connects to.
This issue affects hackney: from 2.0.0-beta.1 before 4.0.1.
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: hackney de benoitc, Description: Vulnerabilidad de bucle con condición de salida inalcanzable ('Bucle Infinito') en benoitc hackney permite asignación excesiva. El analizador de encabezados de respuesta Alt-Svc en src/hackney_altsvc.erl no garantiza el progreso hacia adelante. Cuando parse_token/2 recibe un byte que no es un token, no es un espacio en blanco, no es una coma (p. ej. '!', '@', '=', ';'), devuelve la entrada sin cambios. skip_comma/1 también devuelve el búfer sin cambios cuando el primer byte no es una coma. parse_entries/2 luego recurre con datos idénticos, creando un bucle recursivo de cola infinito y ajustado que fija un planificador al 100% de CPU. El proceso de llamada nunca regresa.
El punto de entrada parse_and_cache/3 se llama sincrónicamente en el proceso de conexión en cada respuesta HTTP. Un encabezado de respuesta Alt-Svc: '!' de un solo byte es suficiente para activar el bloqueo; el encabezado está totalmente controlado por cualquier origen HTTP al que se conecta el cliente.
Este problema afecta a hackney: desde 2.0.0-beta.1 antes de 4.0.1.
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in benoitc hackney allows Excessive Allocation. The Alt-Svc response header parser in src/hackney_altsvc.erl does not guarantee forward progress. When parse_token/2 receives a non-token, non-whitespace, non-comma byte (e.g. !, @, =, ;), it returns the input unchanged. skip_comma/1 also returns the buffer unchanged when the first byte is not a comma. parse_entries/2 then recurses with identical data, creating a tight infinite tail-recursive loop that pins a scheduler at 100% CPU. The calling process never returns.
The entry point parse_and_cache/3 is called synchronously in the connection process on every HTTP response. A single-byte Alt-Svc: ! response header is sufficient to trigger the hang; the header is fully controlled by any HTTP origin the client connects to.
This issue affects hackney: from 2.0.0-beta.1 before 4.0.1.