CVE-2022-40765
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 · uneditedA vulnerability in the Edge Gateway component of Mitel MiVoice Connect through 19.3 (22.22.6100.0) could allow an authenticated attacker with internal network access to conduct a command-injection attack, due to insufficient restriction of URL parameters.
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 · moderate confidenceCommand injection vulnerability in Mitel MiVoice Connect Edge Gateway allows authenticated attackers with internal network access to execute arbitrary OS commands through insufficiently validated URL parameters.
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<= 22.22.6100.0CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/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.
-
Confirm MiVoice Connect installationIdentify whether Mitel MiVoice Connect with Edge Gateway component is installed on the system. Check installed applications or services for MiVoice Connect or Edge Gateway.Affected if MiVoice Connect with Edge Gateway is found on the system
-
Determine installed versionLocate the installed version of MiVoice Connect. Compare your installed version number against the affected range (versions through 22.22.6100.0).Affected if Installed version is 22.22.6100.0 or lower (any version through 19.3/22.22.6100.0)
-
Verify Edge Gateway accessibilityDetermine if the Edge Gateway web interface is exposed to the network. Check firewall rules, network configuration, or listening services to see if Edge Gateway port (typically 443 or 8443) is accessible from internal network segments.Affected if Edge Gateway is reachable from internal network without additional access controls
-
Review logs for suspicious URL patternsExamine Edge Gateway access logs and application logs for unusual or malformed URL parameters that may indicate command injection attempts. Look for patterns involving shell metacharacters in query strings.Affected if Logs contain requests with suspicious URL parameters containing shell metacharacters or unexpected command syntax
-
Check for unauthorized command executionReview system logs, process logs, or audit logs for any unexpected command executions or newly created processes originating from the Edge Gateway service account.Affected if Evidence exists of arbitrary OS commands executed on the system
A system is affected if it runs MiVoice Connect version 22.22.6100.0 or lower with the Edge Gateway component accessible to authenticated internal users.
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.
From vendor dataUpgrade to a patched version of MiVoice Connect beyond 19.3 (22.22.6100.0). Restrict network access to the Edge Gateway to trusted internal users only.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40765 — 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-2022-40765 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