CVE-2024-50603
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOS command injection vulnerability in Aviatrix Controller API endpoints. The /v1/api endpoint accepts unsanitized user input through the cloud_type parameter (list_flightpath_destination_instances) and src_cloud_type parameter (flightpath_connection_test), allowing unauthenticated attackers to inject shell metacharacters and execute arbitrary OS commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.1.4191>= 7.2, < 7.2.4996CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Aviatrix Controller versionLog into the Aviatrix Controller web UI and navigate to Settings > Maintenance > Upgrade, or use the Controller's built-in version check API endpoint. The version number is displayed on the Controller login page or in the system information section.Affected if The installed version is below 7.1.4191, or is 7.2.x but below 7.2.4996.
-
Verify /v1/api endpoint accessibilityCheck network accessibility of the Controller's /v1/api endpoint from untrusted networks. This can be done via curl or a web browser: curl -k https://<controller-ip>/v1/api?action=someaction. Confirm whether the endpoint is reachable from the internet or untrusted internal networks.Affected if The /v1/api endpoint is exposed to unauthenticated/untrusted network access.
-
Check for authentication enforcement on APITest unauthenticated access to the API by sending a request to /v1/api without valid credentials. Observe whether the Controller returns an authentication error or accepts the request.Affected if The Controller accepts API requests without requiring valid authentication credentials.
-
Inspect API request logs for suspicious activityReview Aviatrix Controller logs, particularly access logs and API transaction logs, for unusual requests to /v1/api containing shell metacharacters (such as ;, |, &, $`, or command substitution patterns) in the cloud_type or src_cloud_type parameters.Affected if Log analysis reveals API requests with shell metacharacters in the cloud_type or src_cloud_type parameters, especially from untrusted IP addresses.
You are affected if your Aviatrix Controller version is below 7.1.4191 or falls between 7.2.0 and 7.2.4996, AND the /v1/api endpoint is accessible from untrusted networks without proper authentication enforcement.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.1.41917.2.4996
Upgrade Aviatrix Controller to version 7.1.4191 or later (7.1.x) or 7.2.4996 or later (7.2.x). Apply network controls to restrict access to the Controller's API endpoint if patching cannot be performed immediately.
Upgrade to Controller version 7.1.4191 (or latest 7.1.x) for 7.1.x branch, or version 7.2.4996 (or latest 7.2.x) for 7.2.x branch
- Back up the current Aviatrix Controller configuration before starting the upgrade
- Download the upgrade package for your target version from the Aviatrix support portal (7.1.4191 for 7.1.x branch or 7.2.4996 for 7.2.x branch)
- Access the Aviatrix Controller web interface and navigate to Settings > Maintenance > Upgrade
- Upload the upgrade package and initiate the upgrade process
- Wait for the upgrade to complete and the Controller to reboot
- Log back into the Controller and verify the upgrade was successful by checking the version under Settings > Maintenance > About
- Verify the fix by confirming the Controller version is 7.1.4191 or higher, or 7.2.4996 or higher depending on your branch
- Test that the /v1/api endpoints for list_flightpath_destination_instances and flightpath_connection_test no longer accept shell metacharacters in cloud_type and src_cloud_type parameters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50603 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50603 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data