Browse / AI Framework and Platform Flaws / Denial of service
Denial of service
377 records in AI Framework and Platform Flaws.
- Docling's METS GBS backend is vulnerable to XML Entity Expansion (XXE) attacks Crafted XML inside a tar.gz archive triggers exponential entity expansion during parsing because entity resolution is not disabled, exhausting resources.
- Docling's JATS XML backend is vulnerable to XML Entity Expansion (XXE) attacks The JATS XML parser resolves entities without limits, so a nested entity payload expands exponentially and exhausts resources.
- vm2 Sandbox Access to Host Buffer.alloc Allows timeout Bypass Resulting in Memory Exhaustion Sandboxed code can call the host's Buffer.alloc with a huge size, which the synchronous native call cannot be interrupted by the vm2 timeout, exhausting host memory.
- vm2 has a Sandbox Escape via Promise Constructor Unhandled Rejection (Process Crash DoS) Sandboxed code creates a Promise whose executor triggers an unhandled host-realm error that crashes the Node.js host process, a path the earlier fix missed.
- vLLM: extract_hidden_states speculative decoding crashes server on any request with penalty parameters A speculative decoding proposer returns a wrongly shaped tensor after the first step, so any request with penalty settings crashes the engine process.
- Langflow: DoS Through Lack of File Size Restriction via Deprecated Unauthenticated File Upload API The deprecated unauthenticated upload endpoint applies no size limit, so remote clients can fill disk or memory and cause denial of service.
- PraisonAI has Unrestricted Upload Size in WSGI Recipe Registry Server that Enables Memory Exhaustion DoS The registry server reads request bodies fully into memory based on the client's Content-Length with no upper limit, so large uploads exhaust memory.
- PraisonAI Vulnerable to Decompression Bomb DoS via Recipe Bundle Extraction Without Size Limits Recipe archives are extracted with path checks but no limits on member size or count, so a small, highly compressible bundle can fill the victim's disk.
- Natural Language Toolkit (NLTK) has unbounded recursion in JSONTaggedDecoder.decode_obj() may cause DoS The JSON tagged decoder recurses without a depth limit, so deeply nested input exceeds the recursion limit and crashes the Python process.
- New API has an SQL LIKE Wildcard Injection DoS via Token Search Authenticated users send LIKE patterns with unescaped wildcards to the token search, forcing the database to match and return very large row sets.
- Ray dashboard DELETE endpoints allow unauthenticated browser-triggered DoS (Serve shutdown / job deletion) Browser-request middleware only checks POST and PUT, so a DNS-rebound page can send unauthenticated DELETE requests that shut down Serve or delete jobs.
- llama-index-core vulnerable to Uncontrolled Resource Consumption The directory reader loads every file into memory before applying the file count limit, so large directories exhaust memory.
- Hugging Face Transformers vulnerable to Regular Expression Denial of Service (ReDoS) in the AdamWeightDecay optimizer Attacker-supplied regex patterns in the optimizer's weight-decay filters trigger catastrophic backtracking during matching, hanging the training process.
- Hugging Face Transformers library has Regular Expression Denial of Service A regular expression in the English number normaliser backtracks catastrophically on long digit strings, consuming CPU until the service stalls.
- Hugging Face Transformers is vulnerable to ReDoS through its MarianTokenizer A regular expression in the MarianTokenizer language code removal takes excessive time on crafted strings, pinning the CPU.
- LlamaIndex affected by a Denial of Service (DOS) in JSONReader Deeply nested JSON input causes unbounded recursion in the reader, exceeding Python's recursion limit and exhausting resources or crashing the process.
- vllm API endpoints vulnerable to Denial of Service Attacks An oversized HTTP header on a GET request makes the server buffer the entire value in memory, exhausting available RAM.
- Hugging Face Transformers Regular Expression Denial of Service (ReDoS) vulnerability A catastrophic-backtracking regex in the TensorFlow-to-PyTorch weight name converter lets crafted names consume excessive CPU during conversion.
- Transformers is vulnerable to ReDoS attack through its DonutProcessor class Crafted input strings trigger catastrophic regex backtracking in the Donut token-to-JSON parser, pinning CPU during document processing.
- LlamaIndex vulnerable to DoS attack through uncontrolled recursive JSON parsing Deeply nested JSON passed to the reader causes unbounded recursion that exhausts the stack and crashes the process.
- Transformers vulnerable to ReDoS attack through its SETTING_RE variable A regex used by the chat command has nested quantifiers, so crafted near-matching input causes exponential backtracking and stalls the process.
- Transformers vulnerable to ReDoS attack through its get_imports() function A catastrophic backtracking regex in the import-scanning helper makes crafted Python source consume excessive CPU when model code is loaded.
- Transformers's ReDoS vulnerability in get_configuration_file can lead to catastrophic backtracking A crafted configuration filename triggers catastrophic regex backtracking in the config lookup, consuming CPU and stalling model loading or serving.
- n8n Vulnerable to Denial of Service via Malformed Binary Data Requests Requests to the binary-data endpoint with empty filesystem URIs trigger resource exhaustion, letting an authenticated user make the service unresponsive.
- vLLM DOS: Remotely kill vllm over http with invalid JSON schema An invalid JSON schema in a guided decoding request causes an unhandled exception in the grammar compiler that crashes the engine.
- vLLM allows clients to crash the openai server with invalid regex A client-supplied invalid regex in structured output makes the vLLM OpenAI server crash.
- vLLM vulnerable to Regular Expression Denial of Service Several regular expressions in vLLM backtrack catastrophically on crafted input, so a single request can stall processing.
- Hugging Face Transformers Regular Expression Denial of Service Nested quantifiers in a docstring code-block regex cause catastrophic backtracking on inputs with many newlines, consuming CPU.
- LlamaIndex Vulnerable to Denial of Service (DoS) Recursive link crawling in the web reader lacks an effective max_depth limit, so repeated calls exhaust Python's recursion limit and crash the process.
- Transformers Regular Expression Denial of Service (ReDoS) vulnerability A backtracking regex in the Japanese GPT-NeoX tokenizer takes exponential time on crafted text, pinning CPU and stalling the service.
- PyTorch Improper Resource Shutdown or Release vulnerability A local caller can trigger improper resource release in the CTC loss function, causing the process to stall or crash.
- PyTorch susceptible to local Denial of Service A local call to a max-pool operator with crafted input causes denial of service.
- Ollama Vulnerable to Denial of Service (DoS) via Crafted GZIP A malicious API server returns a gzip bomb that Ollama reads fully into memory, exhausting the server's memory.
- H2O Vulnerable to Denial of Service (DoS) via `HEAD` Request The typeahead endpoint makes an outbound HEAD request with no timeout, so a remote host that hangs can block the server from handling other requests.
- H2O Vulnerable to Denial of Service (DoS) via Large GZIP Parsing Repeatedly uploading and parsing a highly compressed gzip file amplifies data in memory, exhausting resources and stalling the server.
- H2O Vulnerable to Denial of Service (DoS) via `/3/ParseSetup` Endpoint A user-chosen regular expression is applied to attacker-controlled input in the parse setup endpoint, causing catastrophic backtracking that stalls the server.
- H2O Vulnerable to Denial of Service (DoS) via `/3/ImportFiles` Endpoint The ImportFiles endpoint accepts a path that refers back to the same endpoint, so the server recursively calls itself until its request queue is exhausted.
- H2O Vulnerable to Denial of Service (DoS) via `/3/Parse` Endpoint A user-supplied string is compiled as a regular expression and applied to another string, so concurrent requests can exhaust server threads.
- BentoML vulnerable to Uncontrolled Resource Consumption Appending characters to a multipart boundary in a request to the Gradio login route makes the server keep processing input until resources are exhausted.
- BentoML Denial of Service (DoS) via Multipart Boundary Appending dashes to a multipart boundary makes the parser keep processing characters, consuming resources until the service becomes unavailable.
- FastChat Denial of Service vulnerability A multipart upload with an oversized filename overwhelms the FastChat server, making it unavailable to other users.
- FastChat Uncontrolled Resource Consumption vulnerability Extra characters after a multipart boundary cause the server's parser to loop indefinitely, exhausting resources for all users.
- Gradio DOS in multipart boundry while uploading the file A crafted multipart upload with a long run of extra characters after the boundary forces the parser to iterate per character and emit warnings, stalling the server.
- Gradio Vulnerable to Denial of Service (DoS) via Crafted Zip Bomb An uploaded compressed archive expands to a huge size when the dataframe component parses it with pandas, exhausting resources and crashing the server.
- Gradio Vulnerable to Denial of Service (DoS) via Crafted HTTP Request A crafted HTTP request to the Datetime component triggers catastrophic regex backtracking that pins server CPU at full load.
- H2O Vulnerable to Denial of Service (DoS) and File Write The run_tool command's ast-based parser exposes water.tools classes, one of which can stop the server and write large files to arbitrary directories.
- InvokeAI has Denial of Service (DoS) vulnerability in `/api/v1/images/upload` Extra characters after a multipart boundary make the upload endpoint's parser loop forever, halting service for all users.
- InvokeAI Uncontrolled Resource Consumption vulnerability A very large board_name in a PATCH request makes the UI unresponsive and blocks board deletion.
- LiteLLM Vulnerable to Denial of Service (DoS) via Crafted HTTP Request Trailing dash characters appended to a multipart boundary make the proxy's parser loop over each character, exhausting resources without authentication.
- LiteLLM Vulnerable to Denial of Service (DoS) Unauthenticated requests reach an ast.literal_eval call on user-supplied input, which can exhaust resources and crash the LiteLLM server.