Cyber Resilience

CVE-2024-36512

Path Traversal in Fortinet Fortianalyzer 6.2.10 – 7.0.13

Published
14 January 2025
Modified
31 January 2025
Patch / advisory
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.014 70th percentile
Risk Priority 56 floored blend · peak EPSS

Summary

CVE-2024-36512 is a high-severity Path Traversal (CWE-22) vulnerability in Fortinet Fortianalyzer. Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-36512 is a path traversal vulnerability (CWE-22) affecting Fortinet FortiManager and FortiAnalyzer in versions 7.4.0 through 7.4.3, 7.2.0 through 7.2.5, 7.0.2 through 7.0.12, and 6.2.10 through 6.2.13. The issue arises from an improper limitation of a pathname to a restricted directory, which allows remote attackers to execute unauthorized code or commands by sending crafted HTTP or HTTPS requests. Published on January 14, 2025, it carries a CVSS v3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), rated as High severity.

An attacker with high privileges, such as an authenticated administrator, can exploit this vulnerability over the network with low complexity and no user interaction required. Successful exploitation grants high-impact access to confidentiality, integrity, and availability, enabling arbitrary code execution on the affected system and potential full compromise of the FortiManager or FortiAnalyzer instance.

The Fortinet PSIRT advisory FG-IR-24-152 provides details on mitigation strategies and patches; security practitioners should consult https://fortiguard.fortinet.com/psirt/FG-IR-24-152 for upgrade instructions and workarounds applicable to vulnerable versions.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An improper limitation of a pathname to a restricted directory ('path traversal') in Fortinet FortiManager, FortiAnalyzer 7.4.0 through 7.4.3 and 7.2.0 through 7.2.5 and 7.0.2 through 7.0.12 and 6.2.10 through 6.2.13 allows attacker to execute unauthorized code or commands via…

more

crafted HTTP or HTTPS requests.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-36508Same product: Fortinet Fortianalyzer
CVE-2023-25606Same product: Fortinet Fortianalyzer
CVE-2024-33502Same product: Fortinet Fortianalyzer
CVE-2023-44256Same product: Fortinet Fortianalyzer
CVE-2024-32117Same product: Fortinet Fortianalyzer
CVE-2025-68649Same product: Fortinet Fortianalyzer
CVE-2024-52964Same product: Fortinet Fortimanager
CVE-2024-35274Same product: Fortinet Fortianalyzer
CVE-2024-32116Same product: Fortinet Fortianalyzer
CVE-2024-48884Same product: Fortinet Fortimanager

Affected Assets

fortinet
fortianalyzer
6.2.10 — 7.0.13 · 7.2.0 — 7.2.6 · 7.4.0 — 7.4.4
fortinet
fortimanager
6.2.10 — 7.0.13 · 7.2.0 — 7.2.6 · 7.4.0 — 7.4.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes special path elements before pathname construction occurs.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References