CVE-2025-2172
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 · uneditedAviatrix Controller versions prior to 7.1.4208, 7.2.5090, and 8.0.0 fail to sanitize user input prior to passing the input to command line utilities, allowing command injection via special characters in filenames
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 confidenceAviatrix Controller versions prior to 7.1.4208, 7.2.5090, and 8.0.0 contain a command injection vulnerability where user-supplied input in filenames is not sanitized before being passed to command line utilities, allowing attackers to inject arbitrary commands via special characters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- Privileges
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 versionAccess the Aviatrix Controller management interface and navigate to the Settings > Maintenance > About section, or use the controller's API endpoint to retrieve the current software version.Affected if The installed version is lower than 7.1.4208, 7.2.5090, or 8.0.0
-
Confirm controller is accessibleVerify whether the Aviatrix Controller management interface is reachable from network segments outside the trusted administrative zone.Affected if The controller management interface is exposed to untrusted networks, increasing attack surface for command injection attempts
-
Review file operation logsExamine Aviatrix Controller logs for any file upload, export, or filename-related operations that contain unusual characters such as semicolons, pipes, backticks, or dollar signs.Affected if Log analysis reveals file operations with special shell characters that may indicate exploitation attempts
You are affected if your Aviatrix Controller version is prior to 7.1.4208, 7.2.5090, or 8.0.0 and the management interface is accessible to potential attackers.
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 · scopedUpgrade Aviatrix Controller to version 7.1.4208, 7.2.5090, 8.0.0 or later to remediate the command injection vulnerability. If immediate patching is not possible, restrict access to the controller management interface and monitor for suspicious input patterns in file operations.
7.1.4208 or later, 7.2.5090 or later, or 8.0.1 or later (preferably latest stable release)
- 1. Identify the current Aviatrix Controller version running in your environment
- 2. If running version 7.1.x, upgrade to version 7.1.4208 or later
- 3. If running version 7.2.x, upgrade to version 7.2.5090 or later
- 4. If running version 8.0.0, upgrade to version 8.0.1 or later
- 5. If running any earlier version (e.g., 7.0.x or 6.x), plan an upgrade to one of the fixed release branches (7.1.4208+, 7.2.5090+, or 8.0.1+)
- 6. After upgrading, verify the controller is functioning normally and test that the command injection vulnerability is no longer present
- 7. Review Aviatrix release notes for any additional post-upgrade configuration requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2172 — 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-2025-2172 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