CVE-2022-25360
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWatchGuard Firebox and XTM appliances allow an authenticated remote attacker with unprivileged credentials to upload files to arbitrary locations. This vulnerability impacts Fireware OS before 12.7.2_U2, 12.x before 12.1.3_U8, and 12.2.x through 12.5.x before 12.5.9_U2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWatchGuard Firebox and XTM appliances contain an arbitrary file upload vulnerability allowing authenticated users with unprivileged credentials to upload files to arbitrary locations on the filesystem. This path traversal issue in Fireware OS could enable remote code execution or configuration tampering.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 12.0.0, < 12.1.3>= 12.2.0, < 12.5.9>= 12.7.0, < 12.7.2= 12.1.3= 12.5.9= 12.7.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Fireware OS versionLog into the Firebox Web UI or use the CLI command 'fireware -v' or check System > About in the management interface to retrieve the installed Fireware OS version number.Affected if The installed version falls within these ranges: 12.0.0 through 12.1.2, 12.2.0 through 12.5.8, 12.7.0 through 12.7.2, or is exactly 12.1.3, 12.5.9, or 12.7.2.
-
Verify management interface accessibilityConfirm whether the Firebox management interface (HTTP/HTTPS on ports 8080/443 or the standard web UI ports) is reachable from untrusted networks. Check firewall rules and interface bindings in the Network > Interfaces section.Affected if The management interface is exposed to networks outside the trusted internal network or the internet.
-
Review user accounts and privilegesAccess the Firebox management UI, go to Users > User List or use the CLI 'user list' command to enumerate all configured user accounts and their privilege levels.Affected if There are any user accounts with non-administrator or limited privileges that have file upload or configuration permissions enabled.
-
Audit recent configuration changesCheck the Firebox configuration audit log or review the configuration file for any unexpected changes. Use the CLI 'log read' command or access the log viewer in the Web UI to look for configuration modifications around the time of the vulnerability disclosure.Affected if Configuration changes exist that were not made by known administrator accounts, or unusual configuration modifications are present.
A user is affected if their Fireware OS version is any of the versions listed in the affected ranges and the management interface is accessible to untrusted users or contains unprivileged accounts with upload capabilities.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped12.1.312.5.912.7.2
Upgrade Fireware OS to version 12.7.2_U2, 12.1.3_U8, 12.5.9_U2 or later to patch the vulnerability. If immediate patching is not possible, restrict management interface access to trusted networks and monitor for unauthorized configuration changes.
Upgrade to the relevant patched version: 12.1.3_U8, 12.5.9_U2, or 12.7.2_U2 (or later) depending on your current branch
- 1. Identify the currently installed Fireware OS version using the WatchGuard system manager or CLI command 'fireware -v'
- 2. Based on your current version, upgrade to the appropriate patched release:
- - If running 12.0.0 through 12.1.2, upgrade to version 12.1.3_U8 or later
- - If running 12.1.3, upgrade to version 12.1.3_U8 or later
- - If running 12.2.0 through 12.5.8, upgrade to version 12.5.9_U2 or later
- - If running 12.7.0 or 12.7.1, upgrade to version 12.7.2_U2 or later
- 3. Download the appropriate firmware update from the WatchGuard support portal at www.watchguard.com/support/
- 4. Upload and apply the firmware through the Firebox management interface or CLI using the 'firmware upgrade' command
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25360 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data