Cyber Resilience

CVE-2024-35274

Path Traversal in Fortinet Fortianalyzer 6.2.0 – 7.4.3

Path Traversal
Published
12 November 2024
Modified
17 January 2025
Patch / advisory
View advisory
CVSS Score v3.1 2.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 21 floored blend · peak EPSS

Summary

CVE-2024-35274 is a low-severity Relative Path Traversal (CWE-23) vulnerability in Fortinet Fortianalyzer. Its CVSS base score is 2.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 14th percentile by exploit likelihood (below the median); 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.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

An improper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability [CWE-22] in Fortinet FortiAnalyzer versions below 7.4.2, Fortinet FortiManager versions below 7.4.2 and Fortinet FortiAnalyzer-BigData version 7.4.0 and below 7.2.7 allows a privileged attacker with read write…

more

administrative privileges to create non-arbitrary files on a chosen directory via crafted CLI requests.

CWE(s)
CWE-23CWE-22

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.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-32116Same product: Fortinet Fortianalyzer
CVE-2024-32117Same product: Fortinet Fortianalyzer
CVE-2024-32115Same product: Fortinet Fortimanager
CVE-2023-42791Same product: Fortinet Fortimanager
CVE-2024-36508Same product: Fortinet Fortianalyzer
CVE-2023-25606Same product: Fortinet Fortianalyzer
CVE-2024-33502Same product: Fortinet Fortianalyzer
CVE-2024-36512Same product: Fortinet Fortianalyzer
CVE-2023-44256Same product: Fortinet Fortianalyzer
CVE-2024-46664Same vendor: Fortinet

Affected Assets

fortinet
fortianalyzer
6.2.0 — 7.4.3
fortinet
fortianalyzer big data
6.2.1 — 7.4.1
fortinet
fortimanager
6.2.0 — 7.4.3

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

AC-3 Access Enforcement good match

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

SI-10 Information Input Validation good match

Explicit validation of path inputs stops .. sequences from ever being interpreted by the file system.

AC-4 Information Flow Enforcement partial match

Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.

AC-6 Least Privilege partial match

Least privilege reduces the set of reachable files even when a traversal succeeds.

SA-8 Security and Privacy Engineering Principles partial match

Secure-engineering principles require safe pathname construction and input neutralization before any file operation.

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-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent relative traversal.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches path traversal via static/dynamic analysis, but does not itself implement the fix.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against path traversal and other injection flaws.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.

A.8.28 Secure coding partial match
prevents

Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.

References