Cyber Resilience

CVE-2024-46664

Path Traversal in Fortinet Fortirecorder 6.4.0 – 7.0.5

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

Summary

CVE-2024-46664 is a medium-severity Relative Path Traversal (CWE-23) vulnerability in Fortinet Fortirecorder. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 42th 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)

EU & UK References

Vulnerability Data

A relative path traversal in Fortinet FortiRecorder [CWE-23] version 7.2.0 through 7.2.1 and before 7.0.4 allows a privileged attacker to read files from the underlying filesystem via 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.
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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-47566Same product: Fortinet Fortirecorder
CVE-2024-35274Same vendor: Fortinet
CVE-2024-32115Same vendor: Fortinet
CVE-2023-42791Same vendor: Fortinet
CVE-2024-32116Same vendor: Fortinet
CVE-2023-23784Same vendor: Fortinet
CVE-2023-23778Same vendor: Fortinet
CVE-2023-27993Same vendor: Fortinet
CVE-2024-48885Same product: Fortinet Fortirecorder
CVE-2024-48884Same product: Fortinet Fortirecorder

Affected Assets

fortinet
fortirecorder
6.4.0 — 7.0.5 · 7.2.0 — 7.2.2

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.

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

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

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

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.

finds

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

prevents

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

prevents

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

prevents

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

prevents

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

mitigates

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

References