Bug ID 677962: Invalid use of SETTINGS_MAX_FRAME_SIZE

Last Modified: Oct 07, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
14.0.0, 13.1.0, 12.1.3.4

Opened: Aug 10, 2017

Severity: 3-Major

Symptoms

When BIG-IP negotiates settings over HTTP/2 connection, it adopts a value of peer's SETTINGS_MAX_FRAME_SIZE parameter as its own.

Impact

BIG-IP may accept a DATA frame with size above 16,384 bytes violating RFC.

Conditions

A virtual is configured with HTTP/2 profile.

Workaround

There is no workaround at this time.

Fix Information

BIG-IP no longer accepts DATA frames with sizes exceeding a default value of 16,384 bytes.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips