T1499.001 OS Exhaustion Flood

Unter-TechnikEnterprise

Adversaries may launch a denial of service (DoS) attack targeting an endpoint's operating system (OS). A system's OS is responsible for managing the finite resources as well as preventing the entire system from being overwhelmed by excessive demands on its capacity. These attacks do not need to exhaust the actual resources on a system; the attacks may simply exhaust the limits and available resources that an OS self-imposes. Different ways to achieve this exist, including TCP state-exhaustion attacks such as SYN floods and ACK floods. With SYN floods, excessive amounts of SYN packets are sent, but the 3-way TCP handshake is never completed. Because each OS has a maximum number of concurrent TCP connections that it will allow, this can quickly exhaust the ability of the system to receive new requests for TCP connections, thus preventing access to any TCP service provided by the server. ACK floods leverage the stateful nature of the TCP protocol. A flood of ACK packets are sent to the target. This forces the OS to search its state table for a related TCP connection that has already been established. Because the ACK packets are for connections that do not exist, the OS will have to search the entire state table to confirm that no match exists. When it is necessary to do this for a large flood of packets, the computational requirements can cause the server to become sluggish and/or unresponsive, due to the work it must do to eliminate the rogue ACK packets. This greatly reduces the resources available for providing the targeted service.

01

Plattformen

Plattformen, für die dies gilt.

LinuxmacOSWindows
02

Taktiken

ATT&CK-Taktiken, denen diese Technik dient.

03

Unter-Technik von

Die übergeordnete Entität.

04

Gegenmaßnahmen

ATT&CK-Gegenmaßnahmen, die dies verringern.

06

NIST CSF 2.0 — Relevanzbereiche (Protect / Detect)

NIST-CSF-2.0-Bereiche mit dem größten Bezug (belegbasiert).

Abgeleitet aus MITRE CTID (Apache-2.0) und dem NIST-800-53-↔-CSF-Crosswalk (gemeinfrei). Eine indikative Relevanz entlang der Protect-/Detect-Achse — keine Compliance-Bewertung und keine Abdeckungsaussage.

07

Mindernde Maßnahmen (9)

Sicherheitskontrollen, die dies mindern.

08

Angriffsmuster (2)

CAPEC-Angriffsmuster, die dies ausnutzen.

09

Erkannt durch (Sigma) (1)

Zugehörige Sigma-Erkennungsregeln.

10

Quelle

Wo diese Definition veröffentlicht ist.