WatchGuard Firebox iked Out of Bounds Write Vulnerability

We have evidence that suggests this vulnerability is under active exploitation. Indicators of Attack We are providing the following Indicators of Attack (IoAs) to help device owners identify potential attempts to exploit this vulnerability against vulnerable Firebox appliances. These IoAs are only applicable on devices that lack the resolution described later in this advisory. Abnormally large IKE_AUTH request IDi payload With iked diagnostic logging set to the Info logging level, the iked process generates a log message when the Firebox receives an IKE_AUTH request message. An IKE_AUTH request log message with an abnormally large IDi payload size (greater than 100 bytes) is a strong indicator of an attack. The following example diagnostic log shows an example IDi payload size of 300 bytes. 1970-01-01 01:00:00 iked (203.0.113.1<->203.0.113.2)"IKE_AUTH request" message has 6 payloads [ IDi(sz=300) CERT(sz=889) SA(sz=44) TSi(sz=24) TSr(sz=24) N(sz=8)] IKE Process Hang During a successful exploit, the IKED process (responsible for handling IKE negotiations) will hang, interrupting VPN tunnel negotiations and re-keys. This is a strong indicator of attack. Existing tunnels may continue to pass traffic. IKED Process Crash After a failed or successful exploit, the IKED process will crash and generate a fault report on the Firebox. Be aware, there are other situations that could cause the IKED process to crash. This is a weak indicator of attack.