ATTACK-T1498.002Active

Reflection Amplification

Statement

Adversaries may attempt to cause a denial of service (DoS) by reflecting a high-volume of network traffic to a target. This type of Network DoS takes advantage of a third-party server intermediary that hosts and will respond to a given spoofed source IP address. This third-party server is commonly termed a reflector. An adversary accomplishes a reflection attack by sending packets to reflectors with the spoofed address of the victim. Similar to Direct Network Floods, more than one system may be used to conduct the attack, or a botnet may be used. Likewise, one or more reflectors may be used to focus traffic on the target.(Citation: Cloudflare ReflectionDoS May 2017) This Network DoS attack may also reduce the availability and functionality of the targeted system(s) and network.

Reflection attacks often take advantage of protocols with larger responses than requests in order to amplify their traffic, commonly known as a Reflection Amplification attack. Adversaries may be able to generate an increase in volume of attack traffic that is several orders of magnitude greater than the requests sent to the amplifiers. The extent of this increase will depending upon many variables, such as the protocol in question, the technique used, and the amplifying servers that actually produce the amplification in attack volume. Two prominent protocols that have enabled Reflection Amplification Floods are DNS(Citation: Cloudflare DNSamplficationDoS) and NTP(Citation: Cloudflare NTPamplifciationDoS), though the use of several others in the wild have been documented.(Citation: Arbor AnnualDoSreport Jan 2018) In particular, the memcache protocol showed itself to be a powerful protocol, with amplification sizes up to 51,200 times the requesting packet.(Citation: Cloudflare Memcrashed Feb 2018)

Location

Tactic: Impact

Technique Details

Identifier: ATTACK-T1498.002
Parent Technique: ATTACK-T1498
ATT&CK Page: View on MITRE

Tactics

Impact

Platforms

WindowsIaaSLinuxmacOS

Detection

Detection Strategy for Reflection Amplification DoS (T1498.002)

Mitigations

Filter Network Traffic: Employ network appliances and endpoint software to filter ingress, egress, and lateral network traffic. This includes protocol-based filtering, enforcing firewall rules, and blocking or restricting traffic based on predefined conditions to limit adversary movement and data exfiltration. This mitigation can be implemented through the following measures:

Ingress Traffic Filtering:

Use Case: Configure network firewalls to allow traffic only from authorized IP addresses to public-facing servers.
Implementation: Limit SSH (port 22) and RDP (port 3389) traffic to specific IP ranges.

Egress Traffic Filtering:

Use Case: Use firewalls or endpoint security software to block unauthorized outbound traffic to prevent data exfiltration and command-and-control (C2) communications.
Implementation: Block outbound traffic to known malicious IPs or regions where communication is unexpected.

Protocol-Based Filtering:

Use Case: Restrict the use of specific protocols that are commonly abused by adversaries, such as SMB, RPC, or Telnet, based on business needs.
Implementation: Disable SMBv1 on endpoints to prevent exploits like EternalBlue.

Network Segmentation:

Use Case: Create network segments for critical systems and restrict communication between segments unless explicitly authorized.
Implementation: Implement VLANs to isolate IoT devices or guest networks from core business systems.

Application Layer Filtering:

Use Case: Use proxy servers or Web Application Firewalls (WAFs) to inspect and block malicious HTTP/S traffic.
Implementation: Configure a WAF to block SQL injection attempts or other web application exploitation techniques.

EquivalentPartialRelated

SP 800-53

SP800-53-AC-3relatedvia ctid-attack-to-sp800-53

SP800-53-AC-4relatedvia ctid-attack-to-sp800-53

SP800-53-CA-7relatedvia ctid-attack-to-sp800-53

SP800-53-CM-6relatedvia ctid-attack-to-sp800-53

SP800-53-CM-7relatedvia ctid-attack-to-sp800-53

View in graph Report an issue

← Back to Impact

Statement

Ingress Traffic Filtering:

Use Case: Configure network firewalls to allow traffic only from authorized IP addresses to public-facing servers.
Implementation: Limit SSH (port 22) and RDP (port 3389) traffic to specific IP ranges.

Egress Traffic Filtering:

Use Case: Use firewalls or endpoint security software to block unauthorized outbound traffic to prevent data exfiltration and command-and-control (C2) communications.
Implementation: Block outbound traffic to known malicious IPs or regions where communication is unexpected.

Protocol-Based Filtering:

Use Case: Restrict the use of specific protocols that are commonly abused by adversaries, such as SMB, RPC, or Telnet, based on business needs.
Implementation: Disable SMBv1 on endpoints to prevent exploits like EternalBlue.

Network Segmentation:

Use Case: Create network segments for critical systems and restrict communication between segments unless explicitly authorized.
Implementation: Implement VLANs to isolate IoT devices or guest networks from core business systems.

Application Layer Filtering:

Use Case: Use proxy servers or Web Application Firewalls (WAFs) to inspect and block malicious HTTP/S traffic.
Implementation: Configure a WAF to block SQL injection attempts or other web application exploitation techniques.

Reflection Amplification

Statement

Location

Technique Details

Tactics

Platforms

Detection

Mitigations

Cross-Framework Mappings8

Reflection Amplification

Statement

Location

Technique Details

Tactics

Platforms

Detection

Mitigations

Cross-Framework Mappings8