CVE-2024-48884: A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet...
A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiManager 7.6.0 through 7.6.1, FortiManager 7.4.1 through 7.4.3, FortiManager Cloud 7.4.1 through 7.4.3, FortiOS 7.6.0, FortiOS 7.4.0 through 7.4.4, FortiOS 7.2.0 through 7.2.9, FortiOS 7.0.0 through 7.0.15, FortiOS 6.4.0 through 6.4.15, FortiProxy 7.4.0 through 7.4.5, FortiProxy 7.2.0 through 7.2.11, FortiProxy 7.0.0 through 7.0.18, FortiProxy 2.0 all versions, FortiProxy 1.2 all versions, FortiProxy 1.1 all versions, FortiProxy 1.0 all versions may allow a remote authenticated attacker with access to the security fabric interface and port to write arbitrary files or a remote unauthenticated attacker to delete an arbitrary folder
Security readout for executives and security teams
Plain-English summary
CVE-2024-48884 is a Fortinet path traversal flaw affecting FortiOS, FortiProxy, FortiManager, and FortiManager Cloud versions listed by the CVE. It can allow serious disruption, including arbitrary folder deletion without authentication, and file writing by an authenticated attacker with access to the security fabric interface and port.
Executive priority
Prioritize this as a high-risk infrastructure issue because affected Fortinet systems often sit on network control paths. The main business concern is disruption from arbitrary deletion and potential integrity impact from file writes under the stated conditions.
Technical view
The issue is CWE-22 path traversal. The CVSS 3.1 score is 7.1 with network attack vector, low complexity, no user interaction, and high availability impact. The CVE states unauthenticated arbitrary folder deletion is possible, while arbitrary file write requires authenticated access to the security fabric interface and port.
Likely exposure
Exposure is likely where affected FortiOS, FortiProxy, FortiManager, or FortiManager Cloud versions are deployed and relevant management or security fabric interfaces are reachable. Internet-facing or broadly reachable Fortinet administrative planes should be prioritized for review.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation. The CVSS vector includes proof-of-concept exploit maturity, but no source in the bundle confirms real-world exploitation. Treat exploit status as unconfirmed from the available evidence.
Researcher notes
Do not assume all Fortinet products are affected; the bundle names specific FortiOS, FortiProxy, FortiManager, and FortiManager Cloud ranges. Patch targets and operational workarounds are not included in the bundle, so remediation must be confirmed against Fortinet FG-IR-24-259.
Mitigation direction
Identify all Fortinet assets running the affected versions listed in the CVE.
Check Fortinet PSIRT FG-IR-24-259 for fixed releases and vendor-directed workarounds.
Apply Fortinet-supported upgrades or mitigations according to the advisory.
Restrict access to security fabric and management interfaces to trusted administrative networks.
Increase monitoring around Fortinet administrative access and unexpected file or folder changes.
Validation and detection
Compare deployed Fortinet product versions against the CVE affected version ranges.
Confirm whether security fabric interfaces and ports are reachable from untrusted networks.
Review Fortinet administrative logs for unusual authenticated access patterns.
Check filesystem or configuration integrity where Fortinet guidance supports safe validation.
Document assets upgraded, mitigated, or confirmed unaffected.
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 · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.