Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 17.0.0, 17.0.0.1, 17.0.0.2
Fixed In:
15.1.4.1
Opened: Apr 20, 2021 Severity: 2-Critical
If `HTTP2::disable serverside` is called on a flow that has no HTTP2 configured on the server-side then it can incorrectly report an error and RST the flow (this is ID1013597). Because of the timing of this RST, tmm may crash.
Traffic disrupted while tmm restarts.
1) iRule calls `HTTP2::disable serverside` on HTTP_REQUEST. 2) No HTTP2 configured on server-side. 3) server-side has already handled a flow. Or Some internal timing conditions without an iRule involved.
Don't call `HTTP2::disable serverside` (the iRule condition) if there is no HTTP2 on server-side.
None