Bug ID 812989: Queries with TSIG signatures not matching BIG-IP result in malformed BADSIG answer

Last Modified: Dec 13, 2023

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

Known Affected Versions:
14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 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, 15.1.4.1, 15.1.5, 15.1.5.1, 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

Fixed In:
16.0.0

Opened: Aug 06, 2019

Severity: 3-Major

Symptoms

In certain circumstances, it is possible that queries to the BIG-IP system with a TSIG key name, which matches a TSIG key on the BIG-IP system, but carries a different signature, the the BIG-IP system responds with a malformed BADSIG answer

Impact

The BIG-IP system answers with a malformed BADSIG warning; this is an example from the dig command: ;; Warning: Message parser reports malformed message packet. ;; Couldn't verify signature: tsig indicates error.

Conditions

-- Queries to the BIG-IP system are made with a TSIG key name matching a TSIG key on the BIG-IP system, -- The signature on the TSIG key differs.

Workaround

None.

Fix Information

Delete TSIG info after the TSIG error is detected and processed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips