Bug ID 1331257: TMSH should not allow configuring HTTP/3 on Standalone Advanced WAF

Last Modified: Apr 17, 2024

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

Known Affected Versions:
15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4

Opened: Aug 17, 2023

Severity: 4-Minor

Symptoms

Able to configure UDP virtual server with the HTTP/3 on WAF without having the support.

Impact

Without having the support of HTTP/3, able to configure it through TMSH. It creates a confusion while using BIG-IP.

Conditions

- Verify if TMSH should accept a UDP virtual server configuration on a non-LTM licensed BIG-IP (when the GUI dis-allows). - Configure the following HTTP/3 command through TMSH: --------- create ltm virtual vs-http3-test ip-protocol udp destination 3.4.5.7:4433 source-address-translation { type automap } profiles add { udp { context clientside } tcp { context serverside } clientssl-quic { context clientside } serverssl { context serverside } quic { context clientside } http3 { context clientside } http httprouter }

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips