CVE-2024-50603
RCE in Aviatrix Controller ≤ 7.1.4191
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-50603 is a critical-severity OS Command Injection (CWE-78) vulnerability in Aviatrix Controller. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Aviatrix Controller versions prior to 7.1.4191 and 7.2.x prior to 7.2.4996 contain a command injection vulnerability (CWE-78) caused by improper neutralization of special elements in OS commands. The flaw resides in the /v1/api endpoint, where the cloud_type parameter of the list_flightpath_destination_instances action and the src_cloud_type parameter of the flightpath_connection_test action accept unfiltered input that is passed directly to the underlying operating system.
An unauthenticated remote attacker can supply shell metacharacters in either parameter to execute arbitrary commands on the controller with full privileges. Successful exploitation yields complete control over the affected appliance, including the ability to read, modify, or delete data and to pivot into connected cloud networks, matching the CVSS 10.0 rating that reflects network-accessible attack complexity with no required credentials or user interaction.
Vendor advisories direct customers to upgrade immediately to the fixed releases and note that the patches address the command-injection vectors in the flightpath API handlers. The vulnerability appears in the CISA Known Exploited Vulnerabilities catalog, and its EPSS score has reached 0.9436, indicating substantial observed exploitation interest.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44623
Vulnerability Data
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…
more
to /v1/api in cloud_type for list_flightpath_destination_instances, or src_cloud_type for flightpath_connection_test.
- CWE(s)
- KEV Date Added
- 16 January 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.5V1.2.8V15.2.5
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect command sanitization during development.
Input validation directly neutralizes or rejects special characters that would otherwise alter OS command structure.
Least privilege reduces the permissions available to any process that could be subverted by injected commands.
Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.
Secure engineering principles require proper neutralization of untrusted input before command construction.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.