Bug ID 577359: Invalid L4 packets might not match against AFM WhiteList properly

Last Modified: May 01, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP AFM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Opened: Mar 02, 2016
Severity: 3-Major

Symptoms

If BIG-IP receives invalid L4 packets, they might not match against AFM whitelist properly and hence might detect an attack from a known whitelisted IP address.

Impact

The system could detect an attack, even though the packets are coming from a known whitelisted IP address. A false positive on a DoS attack could be triggered. There is no impact to the packet since if the packet is invalid it will be dropped anyway.

Conditions

-- AFM DoS configured. -- DoS "rich" whitelist configured with src IP address. -- Sweep/Flood vector configured with pkt-type "all-pkts". -- The BIG-IP system receives invalid Layer 4 pkts (i.e., IPv6 packets that don't have the correct next-header) specified

Workaround

Instead of AFM DoS "rich" Whitelist, use the DoS AFM Address-List Whitelist to whitelist src IP addresses.

Fix Information

None

Behavior Change