Bug ID 649933: Fragmented RADIUS messages may be dropped

Last Modified: Oct 01, 2018

Bug Tracker

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

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 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, 13.0.0

Fixed In:
13.1.0, 13.0.0 HF1, 12.1.2 HF1, 11.6.2, 11.5.4 HF3

Opened: Mar 09, 2017
Severity: 3-Major

Symptoms

Large RADIUS messages may be dropped when processed by iRules.

Impact

The RADIUS message will be dropped, and an error will be logged that resembles: Illegal argument (line 1) (line 1) invoked from within "RADIUS::avp 61 "integer""

Conditions

This occurs when a RADIUS message that exceeds 2048 bytes is processed by an iRule containing the RADIUS::avp command.

Workaround

Remove RADIUS::avp commands from iRules processing large messages, or ensure that no RADIUS client or server will send large messages.

Fix Information

None

Behavior Change