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 is not being prioritized for NVD enrichment efforts due to resource or other concerns.
Description
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client (HTTP/2 CONTINUATION flood).
When Mint's HTTP/2 receive path observes a HEADERS frame without the END_HEADERS flag, the unparsed header-block fragment is parked in conn.headers_being_processed, and every subsequent CONTINUATION frame on that stream is appended to the accumulator. Nothing in the receive path caps the accumulator: there is no per-stream size limit, no CONTINUATION frame-count limit, and max_header_list_size is only enforced on outgoing requests, never on inbound header blocks (its default is :infinity).
A malicious or compromised HTTP/2 server can stream an endless sequence of CONTINUATION frames (each up to the peer-advertised SETTINGS_MAX_FRAME_SIZE) and drive the client's iolist to arbitrary size, causing memory exhaustion and BEAM process death. A single connection to an attacker-controlled HTTP/2 endpoint is sufficient.
This issue affects mint: from 0.1.0 before 1.9.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: mint de elixir-mint, Description: La vulnerabilidad de asignación de recursos sin límites ni limitación en elixir-mint Mint permite a los servidores HTTP/2 controlados por el atacante agotar la memoria en un cliente Mint (inundación de CONTINUATION de HTTP/2).
Cuando la ruta de recepción HTTP/2 de Mint observa un frame HEADERS sin el flag END_HEADERS, el fragmento de bloque de encabezado no analizado se estaciona en conn.headers_being_processed, y cada frame CONTINUATION subsiguiente en ese flujo se añade al acumulador. Nada en la ruta de recepción limita el acumulador: no hay un límite de tamaño por flujo, ningún límite de conteo de frames CONTINUATION, y max_header_list_size solo se aplica a las solicitudes salientes, nunca a los bloques de encabezado entrantes (su valor predeterminado es :infinity).
Un servidor HTTP/2 malicioso o comprometido puede transmitir una secuencia interminable de frames CONTINUATION (cada uno hasta el SETTINGS_MAX_FRAME_SIZE anunciado por el par) y llevar el iolist del cliente a un tamaño arbitrario, causando agotamiento de memoria y la muerte del proceso BEAM. Una sola conexión a un endpoint HTTP/2 controlado por el atacante es suficiente.
Este problema afecta a mint: desde 0.1.0 antes de 1.9.0.
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client (HTTP/2 CONTINUATION flood).
When Mint's HTTP/2 receive path observes a HEADERS frame without the END_HEADERS flag, the unparsed header-block fragment is parked in conn.headers_being_processed, and every subsequent CONTINUATION frame on that stream is appended to the accumulator. Nothing in the receive path caps the accumulator: there is no per-stream size limit, no CONTINUATION frame-count limit, and max_header_list_size is only enforced on outgoing requests, never on inbound header blocks (its default is :infinity).
A malicious or compromised HTTP/2 server can stream an endless sequence of CONTINUATION frames (each up to the peer-advertised SETTINGS_MAX_FRAME_SIZE) and drive the client's iolist to arbitrary size, causing memory exhaustion and BEAM process death. A single connection to an attacker-controlled HTTP/2 endpoint is sufficient.
This issue affects mint: from 0.1.0 before 1.9.0.
) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
