dbcve.org
Meeting ConnectorApplication · Zoom

CVE-2022-28753

MEDIUM · 5.4 CVSS v3.1 Published 2022-08-11
Fix available
A fix is available. Upgrade to 4.8.129.20220714 or later.
See remediation →
60/100
Remediation priority · Elevated
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
Zoom On-Premise Meeting Connector MMR before version 4.8.129.20220714 contains an improper access control vulnerability. As a result, a malicious actor can join a meeting which they are authorized to join without appearing to the other participants, can admit themselves into the meeting from the waiting room, and can become host and cause other meeting disruptions.

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

Improper access control vulnerability in Zoom On-Premise Meeting Connector MMR allows authenticated users authorized to join a meeting to do so invisibly (not appearing to participants), admit themselves from waiting room, elevate to host privileges, and disrupt meetings. This is an authorization bypass combined with privilege escalation issue.

MitigationUpgrade Zoom On-Premise Meeting Connector MMR to version 4.8.129.20220714 or later to address the improper access control 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
Meeting ConnectorApplication
Affected:< 4.8.129.20220714

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 Zoom Meeting Connector installation
    On the on-premise server, check for Zoom Meeting Connector components. Look for the Zoom MMR service or check installed packages related to Zoom Meeting Connector. Common locations: /opt/zoom or check system services for 'zoom-mmr' or similar.
    Affected if Zoom Meeting Connector MMR software is installed on the system
  2. Determine installed MMR version
    Run the version check command for Zoom Meeting Connector MMR. This is typically done via the Zoom admin interface, command line tools provided by Zoom, or by checking the MMR service version directly. Consult Zoom documentation for the specific command for your version.
    Affected if The installed version is lower than 4.8.129.20220714
  3. Verify MMR component is active
    Check if the MMR (Multipoint Mixer Router) component of the Meeting Connector is running and enabled. This can be verified through the Zoom admin portal for on-premise deployments or by checking the service status on the server.
    Affected if The MMR component is enabled and actively handling meeting sessions
  4. Confirm on-premise deployment
    Verify this is an on-premise Zoom deployment (not Zoom's cloud service). On-premise Meeting Connector is self-hosted and managed by the organization's IT team.
    Affected if The organization uses self-hosted Zoom Meeting Connector infrastructure

A user is affected if they run Zoom Meeting Connector MMR with a version lower than 4.8.129.20220714 on their on-premise deployment, as the authorization bypass requires the vulnerable MMR component to be active.

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.129.20220714 or later
Fixed in 4.8.129.20220714
Interim mitigation

Upgrade Zoom On-Premise Meeting Connector MMR to version 4.8.129.20220714 or later to address the improper access control vulnerability.

Recommended fix High confidence

4.8.129.20220714 or later

  1. Identify all Zoom On-Premise Meeting Connector MMR installations in the environment
  2. Check current version of each MMR installation (versions prior to 4.8.129.20220714 are affected)
  3. Download the fixed version 4.8.129.20220714 or later from Zoom's official portal (explore.zoom.us)
  4. Follow Zoom's standard upgrade procedure for Meeting Connector MMR
  5. After upgrade, verify the version is 4.8.129.20220714 or higher
  6. Test meeting functionality to ensure the access control vulnerability is resolved

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

Fix this in Meeting Connector Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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