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.3 and 4.2.0 through 4.2.6 and 4.0.0 through 4.0.4 allows attacker to execute unauthorized code or commands via crafted HTTP requests.
Credit: psirt@fortinet.com
Affected Software | Affected Version | How to fix |
---|---|---|
Fortinet FortiSandbox Firmware | >=4.4.0<=4.4.3 | |
Fortinet FortiSandbox Firmware | >=4.2.0<=4.2.6 | |
Fortinet FortiSandbox Firmware | >=4.0.0<=4.0.4 | |
Fortinet FortiSandbox Firmware | >=4.0.0<4.0.5 | |
Fortinet FortiSandbox Firmware | >=4.2.0<4.2.7 | |
Fortinet FortiSandbox Firmware | >=4.4.0<4.4.4 |
Please upgrade to FortiSandbox version 4.4.4 or above Please upgrade to FortiSandbox version 4.2.7 or above Please upgrade to FortiSandbox version 4.0.5 or above
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-23671 is considered a critical vulnerability due to its potential to allow unauthorized code execution.
To fix CVE-2024-23671, upgrade Fortinet FortiSandbox to version 4.4.4 or later, 4.2.7 or later, or 4.0.5 or later depending on your current version.
CVE-2024-23671 affects Fortinet FortiSandbox versions 4.4.0 through 4.4.3, 4.2.0 through 4.2.6, and 4.0.0 through 4.0.4.
Yes, CVE-2024-23671 can be exploited through crafted HTTP requests that take advantage of path traversal vulnerabilities.
Organizations using affected versions of Fortinet FortiSandbox are at risk of exploitation from CVE-2024-23671.