CVE-2024-21762: A out-of-bounds write in Fortinet FortiOS versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.6, 7.0.0 through...
A out-of-bounds write in Fortinet FortiOS versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.6, 7.0.0 through 7.0.13, 6.4.0 through 6.4.14, 6.2.0 through 6.2.15, 6.0.0 through 6.0.17, FortiProxy versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.8, 7.0.0 through 7.0.14, 2.0.0 through 2.0.13, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6, 1.0.0 through 1.0.7 allows attacker to execute unauthorized code or commands via specifically crafted requests
Security readout for executives and security teams
Plain-English summary
A memory-safety flaw in affected FortiOS and FortiProxy releases can let an unauthenticated remote attacker run unauthorized code or commands through crafted requests. Successful compromise could expose data, alter security controls, disrupt operations, or provide control of a perimeter appliance.
Executive priority
Treat as an emergency perimeter-security issue. Assign immediate ownership, identify exposed appliances, apply Fortinet's remediation, and investigate potentially exposed systems. Because exploitation is documented by CISA, remediation alone should not replace a compromise assessment.
Technical view
CVE-2024-21762 is a remotely reachable out-of-bounds write, classified as CWE-787. It requires no privileges or user interaction and has a CVSS 3.1 score of 9.6. The supplied record covers multiple FortiOS and FortiProxy release ranges and reports potential compromise of confidentiality, integrity, and availability.
Likely exposure
Exposure is highest where affected FortiOS or FortiProxy appliances accept requests from untrusted networks. The supplied data identifies affected version ranges but does not establish whether every deployment configuration is reachable or vulnerable. Inventory, exact-version, and network-access checks are required.
Exploitation context
CISA lists CVE-2024-21762 in its Known Exploited Vulnerabilities catalog, supporting active exploitation in the wild. The supplied bundle does not describe campaign scope, observed targets, indicators of compromise, or attacker attribution.
Researcher notes
The record supports unauthenticated network exploitation through crafted requests and an out-of-bounds write. It does not provide enough evidence here to characterize the vulnerable component, exploitation mechanics, reliable detection signatures, fixed versions, or post-exploitation behavior. Use the current Fortinet advisory for those details.
Mitigation direction
Consult Fortinet advisory FG-IR-24-015 and move each affected appliance to a vendor-designated fixed release.
Restrict untrusted network access to affected appliances until remediation is complete.
Prioritize internet-facing and business-critical FortiOS and FortiProxy systems.
Preserve relevant appliance and network logs for compromise review.
Validation and detection
Inventory all FortiOS and FortiProxy appliances, including externally managed or standby devices.
Compare exact installed versions against every affected range in the Fortinet advisory.
Confirm whether affected services are reachable from untrusted networks.
Verify upgrades completed successfully and devices now run vendor-designated fixed releases.
Review available logs and vendor guidance for evidence of prior exploitation.
The source record changed after analysis: Material source record changed after analysis.
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.
Exploitation: activeAutomatable: yesTechnical 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-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.