WatchGuard Fireware OS up to 12.5.12+701324/12.11.2 CLI stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in WatchGuard Fireware OS up to 12.5.12+701324/12.11.2. This issue affects some unknown processing of the component CLI. The manipulation results in stack-based overflow. This vulnerability is cataloged as CVE-2025-1547. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability classified as critical has been found in WatchGuard Fireware OS up to 12.5.12+701324/12.11.2. Affected is an unknown function of the component CLI. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
A stack-based buffer overflow vulnerability [CWE-121] in WatchGuard Fireware OS's certificate request command could allow an authenticated privileged user to execute arbitrary code via specially crafted CLI commands.This issue affects Fireware OS: from 12.0 through 12.5.12+701324, from 12.6 through 12.11.2.
The weakness was shared by Cody Sixteen as wgsa-2025-00013. The advisory is shared for download at watchguard.com. This vulnerability is traded as CVE-2025-1547 since 02/21/2025. The exploitability is told to be difficult. It is possible to launch the attack remotely. Additional levels of successful authentication are needed for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 12/11/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-201291). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.6
VulDB Temp Score: 6.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/21/2025 CVE reserved12/05/2025 Advisory disclosed
12/05/2025 VulDB entry created
12/11/2025 VulDB entry last update
Sources
Advisory: wgsa-2025-00013Researcher: Cody Sixteen
Status: Confirmed
CVE: CVE-2025-1547 (🔒)
GCVE (CVE): GCVE-0-2025-1547
GCVE (VulDB): GCVE-100-334404
EUVD: 🔒
Entry
Created: 12/05/2025 02:02Updated: 12/11/2025 03:45
Changes: 12/05/2025 02:02 (67), 12/06/2025 07:44 (1), 12/11/2025 03:45 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.