Skip to main content

Denial of Service

Denial of Service (DoS) is a cyber attack technique that exhausts or disrupts computing, network, or application resources to prevent legitimate users from accessing a system or service.

Expanded Explanation

1. Technical Function and Core Characteristics

DoS refers to intentional actions that degrade or block the availability of a networked service, host, or application by overwhelming resources or exploiting implementation flaws. Attackers use high traffic volumes, protocol abuse, or crafted requests to exhaust bandwidth, processing capacity, memory, or application threads.

Common forms include network-based DoS using large packet floods, application-layer DoS targeting specific Hypertext Transfer Protocol (HTTP), Domain Name System (DNS), or Session Initiation Protocol (SIP) functions, and Distributed Denial of Service (DDoS), in which many compromised systems coordinate traffic. These attacks interfere with availability, which security frameworks classify as a core security property together with confidentiality and integrity.

2. Enterprise Usage and Architectural Context

Enterprises address DoS within security architecture, network engineering, and business continuity planning. Organizations deploy layered controls, including firewalls, intrusion prevention systems, web application firewalls, content delivery networks, and upstream scrubbing services to detect and filter abnormal traffic.

Architects design capacity planning, redundant network paths, anycast routing, and rate limiting to maintain service availability under stress. Security programs integrate DoS risk into incident response runbooks, dependency mapping, and service-level objectives to limit downtime and maintain contractual and regulatory obligations.

3. Related or Adjacent Technologies

DoS relates to DDoS, botnets, and reflection and amplification attacks that misuse protocols such as DNS, NTP, or Self-Service Deployment Portal (SSDP) to multiply traffic toward a target. It also connects to network telemetry, anomaly detection, and Traffic Engineering (TE) tools that classify and reroute flows.

Standards and guidance from organizations such as NIST and ETSI discuss DoS threats in the context of network security controls, secure protocol configuration, and resilience engineering. Security Information and Event Management (SIEM) platforms and DDoS mitigation services integrate with routing infrastructure and cloud edges to coordinate detection and response.

4. Business and Operational Significance

DoS attacks affect uptime, transaction processing, and access to customer-facing and internal services. Outages can interrupt revenue, degrade user experience, delay operations, and interfere with critical services such as authentication, payment processing, and communications.

Regulatory frameworks and industry guidance treat availability as a security and resilience objective, so organizations incorporate DoS scenarios into risk assessments, vendor contracts, and Disaster Recovery (DR) plans. Boards and executives review DoS resilience as part of cyber risk governance and operational continuity oversight.

Related Perspectives

VU#915947: SGLang is vulnerable to remote code execution when rendering chat templates from a model file

April 20, 2026

Overview A remote code execution vulnerability has been discovered in the SGLang project, specifically in the reranking endpoint (/v1/rerank). A CVE has been assigned to track the vulnerability; CVE-2026-5760. An attacker can create a malicious model for SGLang to achieve RCE. Successful exploitation could allow arbitrary code execution in the context of the SGLang service, potentially leading to host compromise, lateral movement, data exfiltration, or denial-of-service (DoS) attacks. No response was obtained from the project maintainers during coordination. Description SGLang is an open-source framework for serving large language models (LLMs) and multimodal AI models, supporting models such as Qwen, DeepSeek, Mistral, and Skywork, and is compatible with OpenAI APIs. A vulnerability, tracked as CVE-2026-5760, has been discovered within the reranking endpoints. Using a cross-encoder model, the reranking endpoint reranks documents based on their relevance to a query. An attacker exploits this vulnerability by creating a malicious GPT Generated Unified Format (GGUF) model file with a crafted tokenizer.chat_template parameter that contains a Jinja2 server-side template injection (SSTI) payload with a trigger phrase to activate the vulnerable code path. A tokenizer.chat_template is a metadata field that defines how text is structured before being processed. The victim then downloads and loads the model in SGLang, and when a request hits the /v1/rerank endpoint, the malicious template is rendered, executing the attacker's arbitrary Python code on the server. This sequence of events enables the attacker to achieve remote code execution (RCE) on the SGLang server. The vulnerability arises from the use of jinja2.Environment() without sandboxing in the getjinjaenv() function. This function sets up the environment for rendering Jinja2 templates, but since it lacks proper sandboxing, it fails to restrict the execution of arbitrary Python code. Consequently, when the reranking endpoint is accessed and a malicious model file containing a crafted tokenizer.chattemplate is loaded, the model can execute arbitrary commands on the server. Impact An attacker can create a malicious model for SGLang to achieve RCE. Successful exploitation could allow arbitrary code execution in the context of the SGLang service, potentially leading to host compromise, lateral movement, data exfiltration, or denial-of-service (DoS) attacks. Deployments that expose the affected interface to untrusted networks are at the highest risk of exploitation. Solution To mitigate this vulnerability, it is recommended to use ImmutableSandboxedEnvironment instead of jinja2.Environment() to render the chat templates. This will prevent the execution of arbitrary Python code on the server. No response or patch was obtained during the coordination process. Acknowledgements Thanks to the reporter, Stuart Beck. This document was written by Christopher Cullen.