WatchGuard Firebox iked Out of Bounds Write Vulnerability
Affects Fireware OS with IKEv2 mobile user VPN or branch office VPN to dynamic gateway peers. Fixed in 12.3.1+722811, 12.5.13, 12.11.4 and 2025.1.1.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 12.11.4, 2025.1.1, 12.3.1+722811, 12.5.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The WatchGuard Fireware OS running on Firebox devices is affected, specifically the iked process used for IKEv2 VPNs, including mobile user VPNs and branch office VPNs configured with a dynamic gateway peer. An unauthenticated remote attacker could exploit this flaw to run arbitrary code on the affected device, potentially giving them full control over it.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
An Out-of-bounds Write vulnerability in the WatchGuard Fireware OS iked process may allow a remote unauthenticated attacker to execute arbitrary code. This vulnerability affects both the mobile user VPN with IKEv2 and the branch office VPN using IKEv2 when configured with a dynamic gateway peer. If the Firebox was previously configured with the mobile user VPN with IKEv2 or a branch office VPN using IKEv2 to a dynamic gateway peer, and both of those configurations have since been deleted, that Firebox may still be vulnerable if a branch office VPN to a static gateway peer is still configured.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- WatchGuard Fireware OS
From 11.0 · through 11.12.4+541730; From 12.0 · fixed in 12.11.4; From 2025.0 · fixed in 2025.1.1
- WatchGuard Fireware OS
From 12.0 · fixed in 12.3.1+722811
- WatchGuard Fireware OS
From 12.0 · fixed in 12.5.13
References 2
psirt.watchguard.com
watchguard.com
Questions about CVE-2025-9242
What does this mean?
The flaw is an out-of-bounds write in the iked IKE service on WatchGuard Firebox appliances. The vendor says a remote attacker who is not logged in may be able to run arbitrary code on the Firebox.Source: psirt.watchguard.com
Am I affected, and how do I check?
The affected products are Fireware OS 11.0 through 11.12.4+541730, 12.0 up to the fixed releases 12.3.1+722811, 12.5.13 and 12.11.4, and 2025.0 up to 2025.1.1. The vulnerable setups are a mobile user VPN using IKEv2 or a branch office VPN using IKEv2 with a dynamic gateway peer. A Firebox that still has a branch office VPN to a static gateway peer after the dynamic configurations were deleted may also be vulnerable. To check, look at the Fireware OS version on the device and whether any IKEv2 mobile or dynamic-peer branch office VPN is configured.Source: psirt.watchguard.com
What should I do about it?
Upgrade to the fixed release for your version line: 2025.1.1, 12.11.4, 12.5.13 or 12.3.1+722811. The facts give no fixed release for the 11.x line, so the vendor's workaround for branch office VPNs to static gateway peers is the only guidance for that line.Source: psirt.watchguard.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-11-12, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data