Endpoint Denial of Service

T1499

Technique with 4 sub-techniques.View on attack.mitre.org

About this technique

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.

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).

To perform DoS attacks against endpoint resources, several aspects apply to multiple methods, including IP address spoofing and botnets.

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.

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.

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.

For attacks attempting to saturate the providing network, see Network Denial of Service.

Detection rules9

Rules on DetectionCode tagged with T1499 or one of its sub-techniques.

Sigma5

RuleLevelLog sourceTechnique
Audit CVE Eventcriticalwindows / NULLT1499.004
Apache Segmentation FaulthighNULL / NULLT1499.004
Nginx Core DumphighNULL / NULLT1499.004
NTFS Vulnerability Exploitationhighwindows / NULLT1499.001
Potential Abuse of Linux Magic System Request Keymediumlinux / NULLT1499

Splunk4

RuleTypeRiskData sourceTechnique
Cisco Secure Firewall - Static Tundra Smart Install AbuseTTPNULLCisco Secure Firewall Threat Defense Intrusion EventT1499
ESXi Bulk VM TerminationTTPNULLVMWare ESXi SyslogT1499
Linux Magic SysRq Key AbuseTTPNULLLinux Auditd Path, Linux Auditd CwdT1499
Ollama Possible Memory Exhaustion Resource AbuseAnomalyNULLOllama ServerT1499

Sub-techniques4

IDNameExamples
T1499.001OS Exhaustion Flood0
T1499.002Service Exhaustion Flood0
T1499.003Application Exhaustion Flood0
T1499.004Application or System Exploitation1

Groups1

Software2

Campaigns0

None recorded.

Procedure examples3

Groups1

Used byProcedure example
GroupSandworm Team

Sandworm Team temporarily disrupted service to Georgian government, non-government, and private sector websites after compromising a Georgian web hosting provider in 2019.

Software2

Used byProcedure example
MalwareOnionDuke

OnionDuke has the capability to use a Denial of Service module.

MalwareZxShell

ZxShell has a feature to perform SYN flood attack on a host.

References5

  1. ArsTechnica Great Firewall of China Open source
    Goodin, D.. (2015, March 31). Massive denial-of-service attack on GitHub tied to Chinese government. Retrieved April 19, 2019.
  2. FSISAC FraudNetDoS September 2012 Open source
    FS-ISAC. (2012, September 17). Fraud Alert – Cyber Criminals Targeting Financial Institution Employee Credentials to Conduct Wire Transfer Fraud. Retrieved September 23, 2024.
  3. FireEye OpPoisonedHandover February 2016 Open source
    Ned Moran, Mike Scott, Mike Oppenheim of FireEye. (2014, November 3). Operation Poisoned Handover: Unveiling Ties Between APT Activity in Hong Kong’s Pro-Democracy Movement. Retrieved November 17, 2024.
  4. Symantec DDoS October 2014 Open source
    Wueest, C.. (2014, October 21). The continued rise of DDoS attacks. Retrieved April 24, 2019.
  5. USNYAG IranianBotnet March 2016 Open source
    Preet Bharara, US Attorney. (2016, March 24). Retrieved April 23, 2019.

Data from MITRE ATT&CK® (Enterprise). ATT&CK® is a registered trademark of The MITRE Corporation.