dbcve.org
Zoom On Premise Meeting Connector MmrApplication · Zoom

CVE-2022-28761

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-14
Fix available
A fix is available. Upgrade to 4.8.20220916.131 or later.
See remediation →
71/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.20220916.131 contains an improper access control vulnerability. As a result, a malicious actor in a meeting or webinar they are authorized to join could prevent participants from receiving audio and video causing 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 an authorized meeting participant to block audio/video transmission to other participants, causing meeting disruptions.

MitigationUpgrade Zoom On-Premise Meeting Connector MMR to version 4.8.20220916.131 or later. Coordinate upgrade during maintenance window to minimize meeting impact.

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
Zoom On Premise Meeting Connector MmrApplication
Affected:< 4.8.20220916.131

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 deployment of Zoom On-Premise Meeting Connector MMR
    Review your Zoom infrastructure documentation or inventory to determine if the On-Premise Meeting Connector MMR component is deployed in your environment. Check Zoom admin interfaces or server inventories for 'Meeting Connector MMR' or 'MMR' components.
    Affected if Zoom On-Premise Meeting Connector MMR is not deployed in your environment, this CVE does not apply.
  2. Locate the installed MMR version
    Access the Zoom On-Premise Meeting Connector MMR server or admin console. Check the software version displayed in the MMR admin interface, or run version inquiry commands if available through the connector management tools. The version is typically visible in the MMR component status or about section.
    Affected if Unable to locate or determine the MMR version indicates the component may not be present or accessible for version verification.
  3. Compare installed version against vulnerable threshold
    Compare the identified MMR version to the affected range: versions earlier than 4.8.20220916.131 are vulnerable. If your version starts with 4.8 and the build number is 20220916.131 or higher, you are on a patched release.
    Affected if Installed MMR version is lower than 4.8.20220916.131, indicating the vulnerability is present.
  4. Verify MMR component is active and processing meetings
    Check the MMR service status to confirm it is running and actively handling meeting audio/video relay functions. Review meeting logs or connector status to confirm the MMR component is actively used.
    Affected if MMR component exists at a vulnerable version but is not active may reduce exposure, though the vulnerability remains present in the software.

Your environment is affected only if Zoom On-Premise Meeting Connector MMR is deployed and the installed version is earlier than 4.8.20220916.131.

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.20220916.131 or later
Fixed in 4.8.20220916.131
Interim mitigation

Upgrade Zoom On-Premise Meeting Connector MMR to version 4.8.20220916.131 or later. Coordinate upgrade during maintenance window to minimize meeting impact.

Recommended fix High confidence

4.8.20220916.131

  1. Identify the current version of Zoom On-Premise Meeting Connector MMR by accessing the admin interface or running the version check command
  2. Download Zoom On-Premise Meeting Connector MMR version 4.8.20220916.131 or later from the official Zoom repository (explore.zoom.us or Zoom's customer portal)
  3. Follow Zoom's standard upgrade procedure for On-Premise Meeting Connector components - typically involves stopping services, replacing the installation files, and restarting services
  4. After upgrade, verify the new version is running by checking the connector's admin interface
  5. Test that meetings function normally with audio and video transmission working properly

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

Fix this in Zoom On Premise Meeting Connector Mmr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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 locally
dbcve dependency scanner

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