Last Modified: Oct 17, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.2.1, 11.4.1, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: May 12, 2016 Severity: 4-Minor
Radius AVP parsing might get out of sync on Vendor-Specific AVP iRules and produce a Tcl error: Buffer error.
Tcl Error and potentially a dropped request. The error is similar to the following: err tmm3[12353]: 01220001:3: TCL error: /Common <CLIENT_ACCEPTED> - Buffer error (line 1) (line 1) invoked from within "RADIUS::avp 26 string vendor-id 9 vendor-type 1.
This occurs when there is an iRule looking for a specific Vendor-Specific AVP, and a Radius Packet that contains a different Vendor-Specific AVP, that comes alphabetically before the one in the iRule.
None.
None