1-minute read
What a defender needs to know
CISA now marks WatchGuard Firebox CVE-2025-14733 as known to be used in ransomware campaigns. The critical out-of-bounds write reaches the Fireware OS iked process through exposed IKEv2 VPN configurations and may let a remote unauthenticated attacker run code. CISA names no ransomware family, operator, victim, attack date, or event count.
WatchGuard observed attackers exfiltrating the active configuration, or a gzip archive containing that configuration and the local management user database. The vendor does not attribute those two variants to the ransomware campaigns in CISA’s newer record.
Install the fixed release for the deployed branch: 2025.1.4, 12.11.6, 12.5.15, or FIPS 12.3.1-b728352; Default 11 builds must be newer than 11.12.4+541730. Deleting dynamic IKEv2 configurations may leave exposure when a static-gateway branch-office VPN remains.
Search the vulnerable interval for 45[.]95[.]19[.]50, 51[.]15[.]17[.]89, 172[.]93[.]107[.]67, 199[.]247[.]7[.]82, 38[.]252[.]8[.]14, and 94[.]249[.]197[.]106. Also find Received peer certificate chain is longer than 8. Reject this certificate chain, an IKE_AUTH request with a CERT payload above 2000 bytes, and iked hangs or crashes. Outbound traffic to a listed address and an oversized certificate payload are strong indicators; a crash alone is weak.
Verify the running version after the update. Review every internet-accessible instance for compromise, preserve its logs and fault reports, and rotate all locally stored Firebox secrets when threat-actor activity is confirmed. A fixed running version confirms the patch is active. Use the evidence review and secret rotation to assess recovery.