Bug ID 781753: WebSocket traffic is transmitted with unknown opcodes

Last Modified: May 29, 2024

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

Known Affected Versions:
13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1

Fixed In:
15.1.0, 14.1.2.8, 13.1.3.2

Opened: May 13, 2019

Severity: 3-Major

Symptoms

The BIG-IP system does not preserve WebSocket frames. Frame headers and payload may be reordered such that a header for a second frame may be sent out in the middle of a first frame's payload. Frame boundaries get skewed and payload gets interpreted as headers.

Impact

WebSocket frames are not preserved such that traffic appears to be garbage. -- If request logging is enabled, client frames may not be preserved. -- If response logging is enabled, server frames may not be preserved.

Conditions

A request logging profile is configured on a WebSocket virtual server.

Workaround

Remove the request logging profile.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips