Bug ID 504633: DTLS should not update 'expected next sequence number' when the record is bad.

Last Modified: Jul 13, 2024

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

Known Affected Versions:
10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.3

Opened: Feb 04, 2015

Severity: 3-Major

Related Article: K16705

Symptoms

DTLS updates the 'expected next sequence number' even if the record is bad. This might cause the unexpected sequence number of good records dropping.

Impact

DTLS might drop the good records that have smaller sequence number packets than the bad records.

Conditions

DTLS receives a bad record with a very large sequence number.

Workaround

None.

Fix Information

The system now updates the 'expected next sequence number' only when the record is good.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips