dbcve.org
GatewayApplication · Aviatrix

CVE-2022-38368

HIGH · 8.8 CVSS v3.1 Published 2022-08-15
Fix available
A fix is available. Upgrade to 6.6.5712 / 6.7.1376 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An issue was discovered in Aviatrix Gateway before 6.6.5712 and 6.7.x before 6.7.1376. Because Gateway API functions mishandle authentication, an authenticated VPN user can inject arbitrary commands.

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 confidence

Command injection vulnerability in Aviatrix Gateway's API functions allows authenticated VPN users to execute arbitrary commands due to improper authentication handling. The flaw enables a low-privilege authenticated user to achieve remote code execution on the affected gateway.

MitigationUpgrade Aviatrix Gateway to version 6.6.5712 or later for the 6.6 branch, or 6.7.1376 or later for the 6.7 branch to resolve the authentication bypass and command injection vulnerability.

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
GatewayApplication
Affected:< 6.6.5712>= 6.7.0, < 6.7.1376

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Aviatrix Gateway is deployed
    Locate Aviatrix Gateway instances in your environment by reviewing network infrastructure, cloud console configurations, or asset inventories that track security appliances.
    Affected if Aviatrix Gateway is not present in the environment, this CVE does not apply.
  2. Identify the Aviatrix Gateway version
    Access the gateway management interface or use administrative commands to retrieve the installed software version. Typical methods include the controller web UI, CLI show commands, or API queries to the gateway.
    Affected if Unable to determine the version - further investigation needed to verify patch status.
  3. Compare version against affected ranges
    Review the version number against the vulnerable ranges: versions below 6.6.5712, or versions 6.7.0 through 6.7.1375.
    Affected if Installed version falls within < 6.6.5712 or >= 6.7.0 and < 6.7.1376 - the environment is affected by this vulnerability.
  4. Check for VPN user authentication enablement
    Review gateway configuration to determine if VPN user authentication features are enabled, as the flaw affects authenticated VPN users.
    Affected if VPN user authentication is enabled on a gateway running an affected version, the command injection vulnerability can be exploited.

A system is affected if it runs Aviatrix Gateway version below 6.6.5712 or between 6.7.0 and 6.7.1375 inclusive, and has VPN user authentication configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.6.5712 / 6.7.1376 or later
Fixed in 6.6.57126.7.1376
Interim mitigation

Upgrade Aviatrix Gateway to version 6.6.5712 or later for the 6.6 branch, or 6.7.1376 or later for the 6.7 branch to resolve the authentication bypass and command injection vulnerability.

Recommended fix High confidence

Upgrade to Aviatrix Gateway version 6.6.5712 (or later 6.6.x) or 6.7.1376 (or later 6.7.x)

  1. 1. Identify the current Aviatrix Gateway version by accessing the Controller and navigating to the Gateway settings.
  2. 2. If running a version < 6.6.5712, plan upgrade to version 6.6.5712 or later.
  3. 3. If running version 6.7.x and < 6.7.1376, plan upgrade to version 6.7.1376 or later.
  4. 4. Review Aviatrix upgrade documentation and release notes for the target version to understand any prerequisites.
  5. 5. Take a backup of the current Gateway configuration before proceeding.
  6. 6. Perform the upgrade following Aviatrix's standard upgrade procedure (typically via the Controller interface or CLI).
  7. 7. After upgrade, verify the Gateway is running the patched version (6.6.5712+ or 6.7.1376+).
  8. 8. Test VPN connectivity and Gateway functionality to confirm normal operation.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38368 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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