Tesla vulnerabilities

Resource exhaustion vulnerability in the Tesla library (Elixir) before version 1.18.3. Tesla.Adapter.Mint.open_conn/2 converts the URL scheme of every request to a BEAM atom without validation, potentially filling the atom table and crashing the VM. An attacker can influence the request URL via redirect features or webhooks.

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in elixir-tesla tesla allows HTTP header injection via Tesla.Multipart.add_content_type_param/2. Tesla.Multipart.add_content_type_param/2 appends caller-supplied strings to the multipart content_type_params list without validating for CR (\r) or LF (\n) characters. Tesla.Multipart.headers/1 then joins these params verbatim with "; " to construct the outgoing Content-Type header value. A param containing \r\n splits the header line, allowing arbitrary headers to be injected into the outbound HTTP request.

Tesla library (Elixir) versions from 1.4.0 before 1.18.3 improperly handle case sensitivity in HTTP headers during cross-origin redirects. The Authorization header in canonical form (e.g., "Authorization") is not filtered, leading to credential leakage to a third-party origin.

Vulnerability in the Tesla library for Elixir (versions 0.6.0 up to before 1.18.3) due to improper handling of highly compressed data (decompression bomb). HTTP responses are decompressed without size limits, and multiple compression layers can lead to exponential data expansion, causing memory exhaustion and denial of service.