Techniques › T1499
T1499 Endpoint Denial of Service
impact — Windows, Linux, macOS, Containers, IaaS · attack.mitre.org · JSON
1
MITRE detection strategy
5
analytics
3
Sigma rules tagged attack.t1499
7
KEV CVEs mapped here
<p>Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users. Endpoint DoS can be performed by exhausting the system resources those services are hosted on or exploiting the system to cause a persistent crash condition. Example services include websites, email services, DNS, and web-based applications. Adversaries have been observed conducting DoS attacks for political purposes and to support other malicious activities, including distraction, hacktivism, and extortion.</p><p>An Endpoint DoS denies the availability of a service without saturating the network used to provide access to the service. Adversaries can target various layers of the application stack that is hosted on the system used to provide the service. These layers include the Operating Systems (OS), server applications such as web servers, DNS servers, databases, and the (typically web-based) applications that sit on top of them. Attacking each layer requires different techniques that take advantage of bottlenecks that are unique to the respective components. A DoS attack may be generated by a single system or multiple systems spread across the internet, which is commonly referred to as a distributed DoS (DDoS).</p><p>To perform DoS attacks against endpoint resources, several aspects apply to multiple methods, including IP address spoofing and botnets.</p><p>Adversaries may use the original IP address of an attacking system, or spoof the source IP address to make the attack traffic more difficult to trace back to the attacking system or to enable reflection. This can increase the difficulty defenders have in defending against the attack by reducing or eliminating the effectiveness of filtering by the source address on network defense devices.</p><p>Botnets are commonly used to conduct DDoS attacks against networks and services. Large botnets can generate a significant amount of traffic from systems spread across the global internet. Adversaries may have the resources to build out and control their own botnet infrastructure or may rent time on an existing botnet to conduct an attack. In some of the worst cases for DDoS, so many systems are used to generate requests that each one only needs to send out a small amount of traffic to produce enough volume to exhaust the target's resources. In such circumstances, distinguishing DDoS traffic from legitimate clients becomes exceedingly difficult. Botnets have been used in some of the most high-profile DDoS attacks, such as the 2012 series of incidents that targeted major US banks.</p><p>In cases where traffic manipulation is used, there may be points in the global network (such as high traffic gateway routers) where packets can be altered and cause legitimate clients to execute code that directs network packets toward a target in high volume. This type of capability was previously used for the purposes of web censorship where client HTTP traffic was modified to include a reference to JavaScript that generated the DDoS code to overwhelm target web servers.</p><p>For attacks attempting to saturate the providing network, see Network Denial of Service.</p>
KEV CVEs mapped to this technique · CTID Mappings Explorer
| CVE | Vendor / product | Mapping type | State | Added |
|---|---|---|---|---|
| CVE-2024-54085 | AMI MegaRAC SPx | primary impact | Mapped | 2025-06-25 |
| CVE-2025-42599 | Qualitia Active! Mail | primary impact | Mapped | 2025-04-28 |
| CVE-2023-6549 | Citrix NetScaler ADC and NetScaler Gateway | primary impact | Mapped | 2024-01-17 |
| CVE-2023-20109 | Cisco IOS and IOS XE | primary impact | Mapped | 2023-10-10 |
| CVE-2023-44487 | IETF HTTP/2 | primary impact | Mapped | 2023-10-10 |
| CVE-2021-35394 | Realtek Jungle Software Development Kit (SDK) | secondary impact | Mapped | 2021-12-10 |
| CVE-2020-5735 | Amcrest Cameras and Network Video Recorder (NVR) | secondary impact | Mapped | 2021-11-03 |
Detection strategy · ATT&CK Enterprise v19.2
- DET0208 Endpoint Resource Saturation and Crash Pattern Detection Across Platforms v1.0
AN0584 WindowsExcessive resource exhaustion or service crash induced by processes launched by users or scripts that rapidly consume CPU/memory or attempt malformed service interactions.WinEventLog:Application
Service crash, unhandled exception, or application hang warnings for critical services (e.g., IIS, DNS, SQL Server)→ DC0038 Application Log ContentWinEventLog:SystemSystem shutdowns due to bugcheck (Event ID 1001) or watchdog timer expirations→ DC0018 Host StatusTunable:TimeWindowServiceTargetCPUThresholdPercentAN0585 LinuxMalicious script or binary causes repeated kernel panics, OOM kills, or systemd service restarts targeting services like nginx, httpd, sshd.journald:systemdRepeated service restart attempts or unit failures→ DC0038 Application Log ContentTunable:ServiceNameRestartThresholdOOMKillCountAN0586 macOSAdversary launches high-entropy process or malformed app bundle causing repeated application crashes and system slowdowns.macos:unifiedlogRepeated process crashes logged by CrashReporter or system instability logs in com.apple.console→ DC0038 Application Log ContentTunable:CrashCountThresholdPayloadEntropyThresholdAN0587 IaaSInstance enters degraded/unhealthy state due to abnormal process load or memory exhaustion, often caused by automation or script-based attacks.AWS:CloudWatchStatusCheckFailed or StatusCheckFailed_System for burstable instances (t2/t3)→ DC0018 Host StatusVPCFlowLogs:AllHigh volume internal traffic with low entropy indicating looped or malicious DoS script→ DC0078 Network Traffic FlowTunable:InstanceTypeFailureThresholdAN0588 ContainersContainer orchestrator logs show crashlooping pods, repeated resource exhaustion, or malicious binaries with infinite loops consuming systemd/cgroup limits.kubernetes:eventsCrashLoopBackOff, OOMKilled, container restart count exceeds threshold→ DC0018 Host Statusdocker:eventsContainer exited with non-zero code repeatedly in short period→ DC0038 Application Log ContentTunable:RestartCountThresholdContainerImageEntropy
Sigma rules · SigmaHQ da9bb07d64, tag attack.t1499
Author: Samuel Monsempes
· 2025-01-08 · logsource: product=windows service=application · 3f2c93c7-7b2a-4d58-bb8d-6f39422d8148
Detects exploitation attempt of CVE-2024-49113 known as LDAP Nightmare, based on "Application Error" log where the faulting application is "lsass.exe" and the faulting module is "WLDAP32.dll".
Author: Milad Cheraghi
· 2025-05-23 · logsource: product=linux service=auditd · ea61bb82-a5e0-42e6-8537-91d29500f1b9
Detects the potential abuse of the Linux Magic SysRq (System Request) key by adversaries with root or sufficient privileges
to silently manipulate or destabilize a system. By writing to /proc/sysrq-trigger, they can crash the system, kill processes,
or disrupt forensic analysis—all while bypassing standard logging. Though intended for recovery and debugging, SysRq can be
misused as a stealthy post-exploitation tool. It is controlled via /proc/sys/kernel/sysrq or permanently through /etc/sysctl.conf.
Author: Swachchhanda Shrawan Poudel (Nextron Systems)
· 2026-06-02 · logsource: product=windows service=application · f8a66a02-4a16-46e5-b7fd-a42c8a93d137
Detects a crash of the LSASS process where netlogon.dll is the faulting module and the exception code is STATUS_STACK_BUFFER_OVERRUN (0xc0000409).
This crash, especially on Domain Controllers, might indicate the exploitation of CVE-2026-41089, a denial of service (DoS) vulnerability,
which exists in the Netlogon component of Windows and can be triggered by sending specially crafted requests to the Netlogon service,
leading to a stack-based buffer overflow and subsequent crash of the LSASS process.