Browse / AI Framework and Platform Flaws / Denial of service
Denial of service
175 records in AI Framework and Platform Flaws.
- NLTK: Quadratic-time CPU denial of service in CCG lexicon parser (fromstring) on wide bracket bodies and operator chains A lexicon parser repeatedly copies remaining input while scanning bracket bodies and operators, so long flat inputs cause quadratic CPU consumption.
- NLTK: Unbounded CPU consumption in SteppingRecursiveDescentParser.parse() with ambiguous or self-embedding grammars The stepping recursive descent parser runs without a time or step limit, so an ambiguous grammar with short input can pin a CPU core indefinitely.
- Kubeflow Pipelines: Pipeline archive upload allows decompression bomb to exhaust server memory Pipeline archive uploads are decompressed without bounding the expanded size, so a small zip or tar file can exhaust API server memory.
- Docling: Unbounded table rowspan/colspan in HTML, JATS, ODS and BoxNote backends causes CPU/memory exhaustion A tiny HTML or spreadsheet file with huge span attributes makes the converter loop and allocate oversized tables, exhausting CPU and memory.
- Docling: METS-GBS archive member limit enforced after full member enumeration (memory exhaustion during format detection) Tar archives have all member headers enumerated into memory before the member-count limit applies, so many empty entries exhaust memory.
- vLLM: Structured-output request errors escape the request boundary and terminate the shared EngineCore — engine-fatal denial of service (3 sites) Malformed structured-output requests raise an uncaught error in the engine loop, which kills the shared engine and blocks all other requests.
- vm2: Host Promise rejection from an exposed constructor can terminate the vm2 host process A rejected promise returned from an exposed host constructor is not marked handled, so Node terminates the host process.
- Open WebUI: Unauthenticated requests can stall the server via uncached OIDC fetches in back-channel logout An unauthenticated back-channel logout request triggers uncached, blocking OIDC discovery and key fetches on the event loop, so repeated requests stall the server.
- Open WebUI: Any authenticated user can start a non-terminating request via a folder parent cycle Re-parenting a folder beneath its own descendant creates a cycle, and the tree walk never tracks visited nodes, so the request never terminates.
- n8n: Prototype Pollution via Workflow Structure Summary Can Lead to Denial of Service Posting a workflow with a reserved key such as __proto__ directly to the REST API pollutes Object.prototype, because the editor's client-side name check is skipped.
- Open WebUI: Any authenticated user can hang the server via message deletion in a cyclic chat tree A chat whose messages reference each other as children makes the message-deletion walk loop forever, blocking the server's event loop.
- NLTK: Pl196xCorpusReader has quadratic ReDoS on malformed TEI blocks Lazy regexes over a TEI block rescan from each unmatched opening tag, so a malformed corpus file causes quadratic CPU growth in reader calls.
- NLTK: Entity-expansion DoS (billion laughs) via remaining raw ElementTree parses Entity-declaring XML handed to several NLTK parsers expands exponentially in memory, exhausting resources, because those call sites bypassed the safe XML parsing helper.
- NLTK: Uncontrolled recursion in nltk.featstruct.FeatStructReader causes unhandled RecursionError (DoS) via deeply nested feature-structure input The featstruct parser recurses on nested brackets with no depth limit, so a short, deeply nested string exhausts the stack and raises an uncaught RecursionError.
- Open WebUI: Instance-wide stall via automation recurrence rules that force multi-second parsing Minutely recurrence rules force the parser to enumerate decades of occurrences synchronously on the event loop, stalling the server for every user.
- vllm has Improper Resource Shutdown or Release Requests to vLLM's OpenAI-compatible serving path trigger a resource release flaw that remote attackers can use to take the server down.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- FastChat Denial of Service vulnerability A multipart upload with an oversized filename overwhelms the FastChat server, making it unavailable to other users.
- 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.
- 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.
- MLflow Uncontrolled Resource Consumption vulnerability Large batches of GraphQL queries repeatedly requesting all runs of an experiment tie up every MLflow worker, blocking other requests.
- Open WebUI denial of service through endpoint for converting markdown An unauthenticated markdown-to-HTML endpoint can be sent payloads that take excessive time to convert, tying up the server.
- Open WebUI Unauthenticated Multipart Boundary Denial of Service (DoS) Vulnerability in api/chat/file A malformed multipart boundary with many trailing characters makes the upload handler process each character endlessly, hanging the server for all users.
- Open WebUI Uncontrolled Resource Consumption vulnerability An unauthenticated endpoint accepts very large content for formatting, so an anonymous client can exhaust server resources until it stops responding.
- Open WebUI Uncontrolled Resource Consumption vulnerability The sign-in form accepts unbounded email and password values, so oversized requests exhaust server CPU, memory and disk without authentication.
- PyTorch Lightning denial of service vulnerability A malformed POST to the LightningApp state endpoint with unexpected values makes the server shut itself down.
- Transformers Regular Expression Denial of Service (ReDoS) vulnerability Crafted input to the Nougat tokenizer's post-processing triggers catastrophic regex backtracking, pinning the CPU and stalling the process.
- ZenML unauthenticated DoS via Multipart Boundry Extra characters appended to multipart boundaries send the parser into an infinite loop, hanging unauthenticated login requests.
- Inefficient Regular Expression Complexity in langflow A regex with catastrophic backtracking runs on attacker-supplied text in an HTTP handler, tying up the server.
- Flowise Unauthenticated Denial of Service (DoS) vulnerability An unauthenticated request to the upload file retrieval endpoint with crafted input crashes the whole Flowise instance.