WatchGuard Firebox and XTM Privilege Escalation Vulnerability (CVE-2022-23176)
Published In CISA KEV since Sources: CVE.org
What is affected, what to do
WatchGuard Firebox and XTM appliances allow a remote attacker with unprivileged credentials to access the system with a privileged management session via exposed management access. This vulnerability impacts Fireware OS before 12.7.2_U1, 12.x before 12.1.3_U3, and 12.2.x through 12.5.x before 12.5.7_U3.
The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.
Conflicting version data — version display is hidden until the data is resolved.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
8.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
8.8
CVSS v3
Severity High on the scale from 0 to 10.
Source: CVE.org
10.8 %
EPSS score
Elevated — model estimates 10-50% exploitation likelihood.
Source: FIRST EPSS, percentile 95.9
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 218.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploited
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 8.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 8.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 10.8 %
- Elevated — model estimates 10-50% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 95.9
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary
Response and mitigation
Why act now?
Prioritisation rationale
The flaw is network-reachable with low complexity and needs only any low-privilege account to obtain a full administrative management session — handing the attacker complete control of the perimeter (policies, VPN, NAT). Perimeter firewalls with internet-facing management are prime targets for botnet building, espionage and pivoting into internal networks; exploitation likelihood sits in the upper tier of all scored CVEs, while CISA has not flagged known ransomware use. Any Firebox with internet-reachable management on unpatched Fireware should be treated as critical with remediation inside 24 h; if management is demonstrably confined to an isolated admin segment, rating it high and patching in the next maintenance window is defensible.
Runbook step 1
Immediate response (0-24 h)
- Inventory exposed devices: Enumerate every WatchGuard Firebox and XTM appliance and confirm whether management access (Fireware Web UI, default TCP 8080; WSM management, default TCP 4117/4118) is reachable from the internet or untrusted segments. Run an external scan of your public IP ranges against these ports.
- Upgrade Fireware OS: Move to a fixed release — 12.7.2_U1 or later (current branch), 12.5.7_U3 for the 12.2.x–12.5.x branch, 12.1.3_U3 for the 12.x through 12.1.x branch. Treat XTM models that no longer receive current Fireware as end-of-life and schedule replacement.
- Lock down management access now: Until patched, remove "Any-External" from the From list of the default "WatchGuard Web UI" and "WatchGuard" policies and allow only dedicated admin source IPs or the management VLAN.
- Rotate credentials: Reset passwords for all Firebox user accounts — especially low-privilege ones (e.g. "Device Monitor" role, status accounts), since these are exactly the entry point this flaw abuses. Then renew admin accounts and locally stored pre-shared keys/VPN secrets if access cannot be ruled out.
- Compromise assessment: Where management was exposed, diff the running configuration against a known-good backup (new users, changed policies, NAT rules, VPN peers, syslog targets). If anything is off, rebuild the device per vendor guidance and assess NIS2 reporting obligations.
Runbook step 2
Mitigation layers
- Network segmentation: Make management interfaces reachable only from a dedicated management VLAN or hardened jump host; explicitly drop traffic from user, guest and DMZ segments to TCP 8080/4117/4118 on firewall interfaces.
- Remote admin via VPN only: Require an authenticated VPN (Mobile VPN/IPsec with MFA) for off-site administration instead of publishing the Web UI to the internet.
- Upstream filtering: If an upstream router or ISP filter exists, add ACLs blocking inbound connections to the Firebox WAN IPs on management ports — this survives an accidental local policy change.
- IAM / least privilege: Cut local Firebox accounts to the minimum, disable unused monitoring/read-only accounts, enforce a strong password policy and use named accounts (no shared logins).
- Configuration hardening: Back up configurations off-box regularly and compare hashes; forward all logs to the SIEM so local log tampering is detectable.
Runbook step 3
Detection rules
- Firebox management logs (syslog): Alert on successful management logins from source IPs outside the admin allowlist. SPL idea:
index=firewall sourcetype=watchguard "Management user" ("logged in" OR "login") NOT src_ip IN (<admin_allowlist>). - Privilege escalation: Sessions where a low-privilege account (Device Monitor/read-only) performs write or configuration actions or obtains admin-level rights; plus any configuration change ("configuration saved", policy/user edits) outside approved change windows.
- Network telemetry (Zeek/NetFlow): Inbound internet connections to firewall WAN IPs on TCP 8080/4117/4118. Zeek idea:
conn.log | id.resp_h in fw_wan_ips and id.resp_p in {8080,4117,4118} and not id.orig_h in admin_nets. - Brute-force / credential-stuffing lead-up: Burst of failed management logins followed by a success from the same source shortly after (Sigma shape: count(failed) > 10 by src_ip, followed by success within 15 min).
- Post-exploitation indicators: New local users, altered syslog destinations, new VPN peers, or unexpected outbound connections originating from the Firebox itself.
- Firebox management logs (syslog): Alert on successful management logins from source IPs outside the admin allowlist. SPL idea:
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
WatchGuard Firebox and XTM appliances allow a remote attacker with unprivileged credentials to access the system with a privileged management session via exposed management access. This vulnerability impacts Fireware OS before 12.7.2_U1, 12.x before 12.1.3_U3, and 12.2.x through 12.5.x before 12.5.7_U3.
Source: cvelistv5, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE)
Vendors and products
Affected operating systems
| Other | watchguard | fireware | 12.1.3 |
| Other | watchguard | fireware | 12.5.7 |
| Other | watchguard | fireware | 12.7.2 |
| Other | watchguard | fireware | — |
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited |
References & sources
- securityportal.watchguard.comx_refsource_MISC, Vendor advisory
- watchguard.comsupport/release-notes/fireware/12/en-US/EN_ReleaseNotes_Firewar…x_refsource_CONFIRM, Release notes, Vendor advisory
- watchguard.comsupport/release-notes/fireware/12/en-US/EN_ReleaseNotes_Firewar…x_refsource_MISC, Release notes, Vendor advisory
- watchguard.comsupport/release-notes/fireware/12/en-US/EN_ReleaseNotes_Firewar…x_refsource_MISC, Release notes, Vendor advisory
- arstechnica.cominformation-technology/2022/04/watchguard-failed-to-disclose-cr…x_refsource_MISC, Third-party advisory
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2022-23176government-resource, US government resource
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2022-23176"><img src="https://intel.neosec.eu/badge/cve/CVE-2022-23176.svg?lang=en" alt="CVE-2022-23176 – NEOSEC Intel" height="20"></a>