CVE-2025-46373: A Heap-based Buffer Overflow vulnerability [CWE-122] vulnerability in Fortinet FortiClientWindows 7.4.0 thr...
A Heap-based Buffer Overflow vulnerability [CWE-122] vulnerability in Fortinet FortiClientWindows 7.4.0 through 7.4.3, FortiClientWindows 7.2.0 through 7.2.8 may allow an authenticated local IPSec user to execute arbitrary code or commands via "fortips_74.sys". The attacker would need to bypass the Windows heap integrity protections
Security readout for executives and security teams
Plain-English summary
A flaw in vulnerable FortiClient for Windows installations could let an already authenticated local IPSec user gain powerful code execution on the endpoint. Exploitation is difficult because Windows heap protections must also be bypassed, but successful compromise could seriously affect confidentiality, integrity, and availability.
Executive priority
Treat this as a high-priority endpoint remediation issue, especially on privileged or sensitive Windows systems using IPSec. It is not described as remotely exploitable without prior local IPSec access, and active exploitation is unconfirmed, but successful exploitation could provide broad system impact. Set a prompt upgrade deadline based on Fortinet's advisory.
Technical view
CVE-2025-46373 is a CWE-122 heap-based buffer overflow involving FortiClient Windows driver fortips_74.sys. It affects versions 7.4.0–7.4.3 and 7.2.0–7.2.8. The CVSS 3.1 score is 7.1 with local access, high complexity, low privileges, no user interaction, changed scope, and high impact.
Likely exposure
Exposure is limited to Windows endpoints running the listed FortiClient versions where an attacker can operate as an authenticated local IPSec user. Internet reachability alone is not sufficient. Inventory should distinguish FortiClient Windows versions and IPSec usage; the supplied evidence does not establish exposure for unlisted versions or products.
Exploitation context
The supplied record is not marked as included in CISA KEV, so active exploitation is not established. Its CVSS temporal vector contains E:P, indicating proof-of-concept maturity in the supplied scoring, but no supporting exploit details are provided. Exploitation also requires bypassing Windows heap-integrity protections.
Researcher notes
The main gating conditions are authenticated local IPSec access, high attack complexity, and bypass of Windows heap-integrity protections. The supplied sources name fortips_74.sys and arbitrary code or command execution but provide no crash mechanics, exploit chain, detection signatures, or confirmed incidents. Fixed versions are not included in the bundle and should be taken directly from Fortinet.
Mitigation direction
Review Fortinet advisory FG-IR-25-125 for the vendor-approved fixed release and upgrade path.
Prioritize upgrades for endpoints running versions 7.4.0–7.4.3 or 7.2.0–7.2.8.
Restrict local access and IPSec authentication to authorized users until remediation is complete.
Apply endpoint monitoring and least-privilege controls to reduce consequences of local compromise.
Validation and detection
Inventory FortiClient Windows versions across managed endpoints.
Identify systems within the affected 7.2 and 7.4 version ranges.
Confirm whether affected endpoints permit authenticated local IPSec use.
Verify remediated endpoints against the fixed-version guidance in Fortinet's advisory.
Review endpoint telemetry for unusual activity associated with FortiClient or fortips_74.sys.
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-122: 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
3Timeline events
1ADP providers
2Source 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-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.