First published: Tue Jan 14 2025(Updated: )
A improper limitation of a pathname to a restricted directory ('path traversal') in Fortinet FortiManager versions 7.6.0 through 7.6.1, 7.4.1 through 7.4.3, FortiOS versions 7.6.0, 7.4.0 through 7.4.4, 7.2.5 through 7.2.9, 7.0.0 through 7.0.15, 6.4.0 through 6.4.15, FortiProxy 7.4.0 through 7.4.5, 7.2.0 through 7.2.11, 7.0.0 through 7.0.18, 2.0.0 through 2.0.14, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6, 1.0.0 through 1.0.7, FortiManager Cloud versions 7.4.1 through 7.4.3 allows attacker to trigger an escalation of privilege via specially crafted packets.
Credit: psirt@fortinet.com
Affected Software | Affected Version | How to fix |
---|---|---|
Fortinet FortiManager | >=7.6.0<=7.6.1 | |
Fortinet FortiManager | >=7.4.1<=7.4.3 | |
Fortinet FortiManager Cloud | >=7.4.1<=7.4.3 | |
Fortinet FortiOS | =. | |
Fortinet FortiOS | >=7.4.0<=7.4.4 | |
Fortinet FortiOS | >=7.2.0<=7.2.9 | |
Fortinet FortiOS | >=7.0.0<=7.0.15 | |
Fortinet FortiOS | >=6.4 | |
Fortinet FortiProxy | >=7.4.0<=7.4.5 | |
Fortinet FortiProxy | >=7.2.0<=7.2.11 | |
Fortinet FortiProxy | >=7.0.0<=7.0.18 | |
Fortinet FortiProxy | >=2.0 | |
Fortinet FortiProxy | >=1.2 | |
Fortinet FortiProxy | >=1.1 | |
Fortinet FortiProxy | >=1.0 | |
Fortinet FortiRecorder | >=7.2.0<=7.2.1 | |
Fortinet FortiRecorder | >=7.0.0<=7.0.4 | |
Fortinet FortiVoice | >=7.0.0<=7.0.4 | |
Fortinet FortiVoice | >=6.4.0<=6.4.9 | |
Fortinet FortiVoice | >=6.0 | |
Fortinet FortiWeb | =. | |
Fortinet FortiWeb | >=7.4.0<=7.4.4 | |
Fortinet FortiWeb | >=7.2 | |
Fortinet FortiWeb | >=7.0 | |
Fortinet FortiWeb | >=6.4 | |
Fortinet FortiManager | >=7.4.1<7.4.4 | |
Fortinet FortiManager | >=7.6.0<7.6.2 | |
Fortinet FortiManager Cloud | >=7.4.1<7.4.4 | |
Fortinet FortiProxy | >=1.0.0<7.0.19 | |
Fortinet FortiProxy | >=7.2.0<7.2.12 | |
Fortinet FortiProxy | >=7.4.0<7.4.6 | |
Fortinet FortiRecorder | >=7.0.0<7.0.5 | |
Fortinet FortiRecorder | >=7.2.0<7.2.2 | |
Fortinet FortiVoice | >=6.0.0<=6.4.10 | |
Fortinet FortiVoice | >=7.0.0<=7.0.5 | |
Fortinet FortiWeb | >=6.4.0<7.4.5 | |
Fortinet FortiWeb | =7.6.0 | |
Fortinet FortiOS | >=6.4.0<7.0.16 | |
Fortinet FortiOS | >=7.2.0<7.2.10 | |
Fortinet FortiOS | >=7.4.0<7.4.5 | |
Fortinet FortiOS | =7.6.0 |
Please upgrade to FortiRecorder version 7.2.2 or above Please upgrade to FortiRecorder version 7.0.5 or above Please upgrade to FortiProxy version 7.4.6 or above Please upgrade to FortiProxy version 7.2.12 or above Please upgrade to FortiProxy version 7.0.19 or above Please upgrade to FortiAuthenticator version 7.0.0 or above Please upgrade to FortiWeb version 7.6.1 or above Please upgrade to FortiWeb version 7.4.5 or above Please upgrade to FortiOS version 7.6.1 or above Please upgrade to FortiOS version 7.4.5 or above Please upgrade to FortiOS version 7.2.10 or above Please upgrade to FortiOS version 7.0.16 or above Please upgrade to FortiManager version 7.6.2 or above Please upgrade to FortiManager version 7.4.4 or above Please upgrade to FortiVoice version 7.2.0 or above Please upgrade to FortiVoice version 7.0.5 or above Please upgrade to FortiVoice version 6.4.10 or above Please upgrade to FortiManager Cloud version 7.4.4 or above
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-48884 has been classified with a critical severity due to its potential impact on path traversal vulnerabilities.
CVE-2024-48884 affects Fortinet FortiManager, FortiOS, FortiProxy, and FortiRecorder across multiple versions leading up to their respective patches.
To fix CVE-2024-48884, upgrade FortiManager to version 7.6.2 or later, and other affected products to their respective patched versions.
Using software vulnerable to CVE-2024-48884 poses significant security risks, and immediate remediation through updates is strongly advised.
There are no known workarounds for CVE-2024-48884; updating the software is the only effective measure to mitigate the vulnerability.