CVE-2025-1547: WatchGuard Firebox Authenticated Stack Overflow in Certificate Request Command
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.
Security readout for executives and security teams
Plain-English summary
A privileged Firebox administrator could abuse a certificate request command to run unauthorized code on the appliance. Successful exploitation could compromise the confidentiality, integrity, and availability of firewall operations. The supplied evidence does not establish unauthenticated access or active exploitation.
Executive priority
Treat this as a high-priority verification and remediation task, especially where management access is broadly reachable or privileged credentials may be exposed. It is serious because code execution could affect a security gateway, but the available evidence does not justify declaring an active exploitation emergency.
Technical view
CVE-2025-1547 is a CWE-121 stack-based buffer overflow in the Fireware OS certificate request command. Specially crafted CLI input from an authenticated privileged user may enable arbitrary code execution. Its CVSS 4.0 score is 7.5, with high complexity, a required preparatory condition, high privileges, and no user interaction.
Likely exposure
Exposure is limited to WatchGuard Firebox environments running affected Fireware OS releases where privileged users can reach the CLI. The bundle lists version 12.0 but also marks it unaffected, so the precise affected version range cannot be reliably determined from the supplied evidence.
Exploitation context
Exploitation requires authenticated privileged access, high complexity, and an additional preparatory condition. The CVE is not listed as KEV in the bundle, and no supplied source establishes active exploitation. Compromised administrator credentials or malicious insiders could increase practical risk.
Researcher notes
The supplied affected-product data is internally inconsistent: version 12.0 appears twice while default status is “unaffected.” Confirm release-level scope directly with WatchGuard. No patch version, workaround, proof of concept, or exploitation evidence is established by the bundle; avoid inferring any of these.
Mitigation direction
Consult the WatchGuard advisories for confirmed affected builds and vendor-approved remediation.
Apply the vendor-recommended Fireware OS update when applicable.
Restrict CLI and management access to trusted administrative networks.
Remove unnecessary privileged accounts and strengthen administrator authentication.
Monitor privileged certificate-management activity for suspicious commands or unexpected changes.
Validation and detection
Inventory Firebox appliances and record each exact Fireware OS version and build.
Compare installed builds with WatchGuard's current affected-version guidance.
Verify management and CLI interfaces are inaccessible from untrusted networks.
Review privileged accounts, authentication records, and recent administrative access.
Investigate unusual certificate requests, appliance crashes, or unexplained configuration changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
4Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.