Bug ID 762205: IKEv2 rekey fails to recognize VENDOR_ID payload when it appears

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,, 15.0.0, 15.0.1,,,

Fixed In:

Opened: Mar 19, 2019
Severity: 2-Critical


Rekey with non BIG-IP systems can fail when a response contains a VENDOR_ID payload.


BIG-IP as the initiator of rekey drops the rekey negotiation without making further progress when the responder included a VENDOR_ID payload in a response. This will result in deleting the SA for good when the hard lifetime expires, causing a tunnel outage.


- IKEv2 Responder sends VENDOR_ID payload in rekey response. - The ipsec.log misleadingly reports: [I] [PROTO_ERR]: unexpected critical payload (type 43) Note: This message may be correctly present under other conditions, with different type constants not equal to 43.


No workaround is known at this time.

Fix Information

Handling of payload types during rekey will now ignore VENDOR_ID when it appears, the same way we ignore VENDOR_ID in other messages during IKE negotiation.

Behavior Change