dbcve.org
Meeting ConnectorApplication · Zoom

CVE-2022-28750

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-11
Fix available
A fix is available. Upgrade to 4.8.20220419.112 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Zoom On-Premise Meeting Connector Zone Controller (ZC) before version 4.8.20220419.112 fails to properly parse STUN error codes, which can result in memory corruption and could allow a malicious actor to crash the application. In versions older than 4.8.12.20211115, this vulnerability could also be leveraged to execute arbitrary code.

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

Zoom On-Premise Meeting Connector Zone Controller fails to properly parse STUN (Session Traversal Utilities for NAT) error codes, leading to memory corruption. This can be exploited to crash the application (DoS), and in versions older than 4.8.12.20211115, could allow arbitrary code execution due to the memory corruption vulnerability.

MitigationUpgrade Zoom On-Premise Meeting Connector Zone Controller to version 4.8.20220419.112 or later (preferably 4.8.12.20211115 or later to address the RCE vector). This is a critical priority given the CVSS 9.8 score and network-exploitable nature.

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
Meeting ConnectorApplication
Affected:< 4.8.20220419.112

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
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 checks

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

  1. Identify if Zoom Meeting Connector is installed
    Check the system for Zoom Meeting Connector components - look for 'Meeting Connector' or 'Zone Controller' processes or installed packages on the On-Premise server
    Affected if Zoom Meeting Connector Zone Controller software is present on the system
  2. Determine the installed version
    Use system commands or Zoom administrative tools to query the installed version of the Zoom Meeting Connector software
    Affected if The installed version number is lower than 4.8.20220419.112
  3. Verify STUN feature is in use
    Check if STUN (Session Traversal Utilities for NAT) is enabled in the Zoom Meeting Connector configuration or network settings
    Affected if STUN handling is enabled and the connector processes STUN traffic from external sources
  4. Review network exposure
    Determine if the Meeting Connector is exposed to external network traffic (internet-facing or receives STUN packets from untrusted sources)
    Affected if The connector can receive STUN packets from external/network sources without proper filtering
  5. Check for application crashes
    Review system logs and crash dumps for any unexpected process terminations of the Meeting Connector service
    Affected if The application has crashed or experienced memory corruption errors

The environment is affected if Zoom Meeting Connector Zone Controller is installed and its version is lower than 4.8.20220419.112, with STUN feature enabled and exposed to network traffic.

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 4.8.20220419.112 or later
Fixed in 4.8.20220419.112
Interim mitigation

Upgrade Zoom On-Premise Meeting Connector Zone Controller to version 4.8.20220419.112 or later (preferably 4.8.12.20211115 or later to address the RCE vector). This is a critical priority given the CVSS 9.8 score and network-exploitable nature.

Recommended fix High confidence

4.8.20220419.112 or later

  1. 1. Identify the current version of the Zoom On-Premise Meeting Connector Zone Controller (ZC) by accessing the administration interface or checking system documentation.
  2. 2. Navigate to the Zoom official support or download portal (explore.zoom.us) and locate the Meeting Connector download page.
  3. 3. Download the Meeting Connector Zone Controller version 4.8.20220419.112 or a later stable release.
  4. 4. Back up the current Meeting Connector configuration and database as a precautionary measure before upgrading.
  5. 5. Install the downloaded version following the standard Zoom Meeting Connector upgrade procedures documented in the Zoom On-Premise Administrator Guide.
  6. 6. After installation completes, verify the new version number displays as 4.8.20220419.112 or later in the Zone Controller administration interface.
  7. 7. Test STUN connectivity and verify the Zone Controller is functioning normally without crashes.

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

Fix this in Meeting Connector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28750 — 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-28750 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