CVE-2024-52963: A out-of-bounds write in Fortinet FortiOS versions 7.6.0, 7.4.0 through 7.4.6, 7.2.0 through 7.2.10, 7.0.0...
A out-of-bounds write in Fortinet FortiOS versions 7.6.0, 7.4.0 through 7.4.6, 7.2.0 through 7.2.10, 7.0.0 through 7.0.16, 6.4.0 through 6.4.15 allows attacker to trigger a denial of service via specially crafted packets.
Security readout for executives and security teams
Plain-English summary
CVE-2024-52963 is a Fortinet memory handling flaw that can let a remote, unauthenticated attacker crash or disrupt affected devices using specially crafted packets. The documented impact is limited to availability, not data theft or takeover. Business urgency is highest where affected Fortinet systems protect critical network paths.
Executive priority
Treat as a controlled, near-term infrastructure maintenance item, not an emergency breach event. Prioritize systems where downtime would disrupt business operations. Confirm vendor fixes or workarounds before scheduling changes.
Technical view
The issue is a CWE-787 out-of-bounds write in affected Fortinet firmware. CVSS 3.1 score is 3.5, with network attack vector, high attack complexity, no privileges, no user interaction, and low availability impact. The source bundle lists FortiOS, FortiProxy, and FortiPAM affected version families, though the description emphasizes FortiOS.
Likely exposure
Exposure likely exists where listed Fortinet versions are deployed, especially internet-facing or perimeter devices. Affected FortiOS ranges include 7.6.0, 7.4.0-7.4.6, 7.2.0-7.2.10, 7.0.0-7.0.16, and 6.4.0-6.4.15. The bundle also lists FortiProxy and FortiPAM versions; confirm against Fortinet guidance.
Exploitation context
The source bundle does not show CISA KEV listing, and it provides no evidence of active exploitation. The CVSS vector includes functional exploit maturity, but exploitation requires high complexity and is described as causing denial of service only.
Researcher notes
Evidence is limited to denial of service from crafted packets. Do not assume code execution or data compromise from the provided sources. There is a product-scope inconsistency: the title emphasizes FortiOS, while affected data also lists FortiProxy and FortiPAM; validate against FG-IR-24-373.
Mitigation direction
Check Fortinet PSIRT FG-IR-24-373 for fixed versions and workarounds.
Prioritize remediation for internet-facing or business-critical Fortinet appliances.
Reduce unnecessary external exposure to affected management or service interfaces.
Monitor Fortinet and Siemens advisories for product-specific update guidance.
Plan maintenance windows for upgrades where vendor guidance identifies affected versions.
Validation and detection
Inventory FortiOS, FortiProxy, and FortiPAM versions in production.
Compare installed versions with the affected ranges in Fortinet’s advisory.
Identify devices exposed to untrusted networks or critical traffic paths.
Check monitoring for unexplained crashes, restarts, or packet-triggered service disruption.
Document compensating controls if immediate upgrade is not possible.
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-787: 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.
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.
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-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.