First published: Tue Apr 09 2024(Updated: )
A improper limitation of a pathname to a restricted directory ('path traversal') in Fortinet FortiSandbox version 4.4.0 through 4.4.4 and 4.2.0 through 4.2.6 and 4.0.0 through 4.0.5 and 3.2.0 through 3.2.4 and 3.1.0 through 3.1.5 and 3.0.0 through 3.0.7 and 2.5.0 through 2.5.2 and 2.4.0 through 2.4.1 may allows attacker to information disclosure via crafted http requests.
Credit: psirt@fortinet.com
Affected Software | Affected Version | How to fix |
---|---|---|
Fortinet FortiSandbox | >=4.4.0<=4.4.4 | |
Fortinet FortiSandbox | >=4.2.0<=4.2.6 | |
Fortinet FortiSandbox | >=4.0 | |
Fortinet FortiSandbox | >=3.2 | |
Fortinet FortiSandbox | >=3.1 | |
Fortinet FortiSandbox | >=3.0 | |
Fortinet FortiSandbox | >=2.5 | |
Fortinet FortiSandbox | >=2.4 | |
Fortinet FortiSandbox | >=2.4.0<4.2.7 | |
Fortinet FortiSandbox | >=4.4.0<4.4.5 |
Please upgrade to FortiSandbox version 4.4.5 or above Please upgrade to FortiSandbox version 4.2.7 or above
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-31487 is classified with a high severity due to its path traversal vulnerability allowing unauthorized access to restricted directories.
To mitigate CVE-2024-31487, upgrade Fortinet FortiSandbox to version 4.4.5 or higher, 4.2.7 or higher, or ensure you are using a version not affected by the vulnerability.
CVE-2024-31487 affects multiple Fortinet FortiSandbox versions including 4.4.0 through 4.4.4 and several earlier major versions as listed in the vulnerability release.
Yes, CVE-2024-31487 could potentially lead to data breaches by allowing attackers to access unauthorized files on the system.
There is no official workaround for CVE-2024-31487; the recommended action is to upgrade to secure versions immediately.