MITRE ATT&CK / Techniques / T1499.002

Endpoint Denial of Service: Service Exhaustion Flood

ID
T1499.002
Tactics
TA0040 Impact
Sub-technique of
T1499 Endpoint Denial of Service
Platforms
Windows, IaaS, Linux, macOS
Data sources
Application Log Content, Network Connection Creation, Host Status, Process Access, Network Traffic Flow, Network Traffic Content, Firewall Rule Modification
Source
attack.mitre.org
MITRE last modified
25 Oct 2025

Adversaries may target the different network services provided by systems to conduct a denial of service (DoS). Adversaries often target the availability of DNS and web services, however others have been targeted as well.[2] Web server software can be attacked through a variety of means, some of which apply generally while others are specific to the software being used to provide the service.

One example of this type of attack is known as a simple HTTP flood, where an adversary sends a large number of HTTP requests to a web server to overwhelm it and/or an application that runs on top of it. This flood relies on raw volume to accomplish the objective, exhausting any of the various resources required by the victim software to provide the service.[3]

Another variation, known as a SSL renegotiation attack, takes advantage of a protocol feature in SSL/TLS. The SSL/TLS protocol suite includes mechanisms for the client and server to agree on an encryption algorithm to use for subsequent secure connections. If SSL renegotiation is enabled, a request can be made for renegotiation of the crypto algorithm. In a renegotiation attack, the adversary establishes a SSL/TLS connection and then proceeds to make a series of renegotiation requests. Because the cryptographic renegotiation has a meaningful cost in computation cycles, this can cause an impact to the availability of the service when done in volume.[4]

Detection

Mitigations (1)

M1037 Filter Network Traffic

Leverage services provided by Content Delivery Networks (CDN) or providers specializing in DoS mitigations to filter traffic upstream from services.[1] Filter boundary traffic by blocking source addresses sourcing the attack, blocking ports that are being targeted, or blocking protocols being used for transport.

References

  1. CERT-EU DDoS March 2017
  2. Arbor AnnualDoSreport Jan 2018
  3. Cloudflare HTTPflood
  4. Arbor SSLDoS April 2012