CVE-2024-35276: A stack-based buffer overflow vulnerability in Fortinet FortiAnalyzer 7.4.0 through 7.4.3, FortiAnalyzer 7....
A stack-based buffer overflow vulnerability in Fortinet FortiAnalyzer 7.4.0 through 7.4.3, FortiAnalyzer 7.2.0 through 7.2.5, FortiAnalyzer 7.0.0 through 7.0.12, FortiAnalyzer 6.4.0 through 6.4.14, FortiAnalyzer Cloud 7.4.1 through 7.4.3, FortiAnalyzer Cloud 7.2.1 through 7.2.5, FortiAnalyzer Cloud 7.0.1 through 7.0.11, FortiAnalyzer Cloud 6.4 all versions, FortiManager 7.4.0 through 7.4.3, FortiManager 7.2.0 through 7.2.5, FortiManager 7.0.0 through 7.0.12, FortiManager 6.4.0 through 6.4.14, FortiManager Cloud 7.4.1 through 7.4.3, FortiManager Cloud 7.2.1 through 7.2.5, FortiManager Cloud 7.0.1 through 7.0.11, FortiManager Cloud 6.4 all versions allows attacker to execute unauthorized code or commands via specially crafted packets.
Security readout for executives and security teams
Plain-English summary
Fortinet FortiManager and FortiAnalyzer versions listed in the CVE have a stack-based buffer overflow that can let an unauthenticated network attacker run unauthorized code or commands using specially crafted packets. The CVSS score is medium, but these products often manage security infrastructure, so exposed or business-critical deployments deserve prompt attention.
Executive priority
Treat this as a near-term remediation item, especially where Fortinet management platforms are exposed or operationally critical. It is not KEV-listed in the supplied data, but unauthenticated network code execution risk on security management infrastructure warrants focused tracking.
Technical view
CVE-2024-35276 is CWE-121 stack-based buffer overflow affecting FortiManager, FortiManager Cloud, FortiAnalyzer, and FortiAnalyzer Cloud across 6.4, 7.0, 7.2, and 7.4 ranges listed by Fortinet/CVE. The vector is network, no privileges, no user interaction, high attack complexity, unchanged scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to organizations running the affected FortiManager or FortiAnalyzer product/version ranges, including listed Cloud variants. Internet-reachable management or collector interfaces would increase concern, but the supplied sources do not identify specific exposed ports or deployment prerequisites.
Exploitation context
The CVSS vector marks exploit code maturity as proof-of-concept, but CISA KEV status is false in the supplied bundle. There is no source-backed evidence here of active exploitation. The vulnerability requires specially crafted packets and high attack complexity.
Researcher notes
Evidence is limited to CVE metadata and Fortinet PSIRT reference data. The sources identify affected version ranges and impact, but do not provide packet details, affected interfaces, or exploit prerequisites beyond high attack complexity. Avoid assuming active exploitation without additional source confirmation.
Mitigation direction
Check Fortinet FG-IR-24-165 for the vendor-approved upgrade or remediation path.
Prioritize affected FortiManager and FortiAnalyzer systems that are externally reachable or centrally manage security controls.
Confirm FortiManager Cloud and FortiAnalyzer Cloud tenant remediation status with Fortinet support or service notices.
Limit access to affected management services to trusted administrative networks while applying vendor guidance.
Validation and detection
Inventory FortiManager, FortiAnalyzer, FortiManager Cloud, and FortiAnalyzer Cloud versions against the listed affected ranges.
Verify whether any affected service is reachable from untrusted networks.
Confirm the deployed version is outside the vulnerable ranges after remediation.
Review appliance logs for unexpected crashes or anomalous management-plane activity.
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.
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-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.