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.
Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in benoitc hackney allows HTTP Request/Response Splitting. The WebSocket upgrade code in src/hackney_ws.erl copies the host, path, headers (ExtraHeaders), and protocols options from the caller-supplied opts map into the internal #ws_data{} record in init/1 and then splices them verbatim into the raw HTTP/1.1 upgrade request by binary concatenation in do_handshake/1. No CRLF or NUL stripping is performed at any of these four injection sites. An attacker who controls any of these options — for example by forwarding URL components or header values from untrusted input into hackney_ws:start_link/1 — can inject arbitrary HTTP headers into the outbound WebSocket upgrade request, leading to header injection, credential spoofing toward the upstream server, log and cache poisoning, or request smuggling via intermediary proxies.
This issue affects hackney: from 2.0.0 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: La vulnerabilidad de Neutralización Inadecuada de Secuencias CRLF ('Inyección CRLF') en benoitc hackney permite la División de Solicitudes/Respuestas HTTP. El código de actualización de WebSocket en src/hackney_ws.erl copia las opciones de host, ruta, encabezados (ExtraHeaders) y protocolos del mapa de opciones (opts map) proporcionado por el llamador en el registro interno #ws_data{} en init/1 y luego los empalma textualmente en la solicitud de actualización HTTP/1.1 sin procesar mediante concatenación binaria en do_handshake/1. No se realiza ninguna eliminación de CRLF o NUL en ninguno de estos cuatro sitios de inyección. Un atacante que controla cualquiera de estas opciones - por ejemplo, reenviando componentes de URL o valores de encabezado de entrada no confiable a hackney_ws:start_link/1 - puede inyectar encabezados HTTP arbitrarios en la solicitud de actualización de WebSocket saliente, lo que lleva a la inyección de encabezados, suplantación de credenciales hacia el servidor ascendente, envenenamiento de registros y caché, o contrabando de solicitudes a través de proxies intermediarios.
Este problema afecta a hackney: desde 2.0.0 antes de 4.0.1.
Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in benoitc hackney allows HTTP Request/Response Splitting. The WebSocket upgrade code in src/hackney_ws.erl copies the host, path, headers (ExtraHeaders), and protocols options from the caller-supplied opts map into the internal #ws_data{} record in init/1 and then splices them verbatim into the raw HTTP/1.1 upgrade request by binary concatenation in do_handshake/1. No CRLF or NUL stripping is performed at any of these four injection sites. An attacker who controls any of these options — for example by forwarding URL components or header values from untrusted input into hackney_ws:start_link/1 — can inject arbitrary HTTP headers into the outbound WebSocket upgrade request, leading to header injection, credential spoofing toward the upstream server, log and cache poisoning, or request smuggling via intermediary proxies.
This issue affects hackney: from 2.0.0 before 4.0.1.