Zoom On Premise Meeting Connector MmrApplication · Zoom

CVE-2022-28759

HIGH · 8.6 CVSS v3.1 Published 2022-10-14
Fix available
A fix is available. Upgrade to 4.8.20220815.130 or later.
See remediation →
95/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 MMR before version 4.8.20220815.130 contains an improper access control vulnerability. As a result, a malicious actor could obtain the audio and video feed of a meeting they were not authorized to join 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 unauthorized users to access meeting audio/video feeds they are not authorized to join, potentially exposing sensitive meeting content.

MitigationUpgrade Zoom On-Premise Meeting Connector MMR to version 4.8.20220815.130 or later to remediate the access control flaw.

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.20220815.130

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

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

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. Verify Zoom On-Premise Meeting Connector MMR is installed
    Check system packages or installed software list for 'Zoom On Premise Meeting Connector MMR' or related MMR components
    Affected if The product is not present on the system (not affected)
  2. Determine installed MMR version
    Run command to retrieve MMR version: rpm -qa | grep -i zoom or check installed package version through system package manager
    Affected if Version number returned is lower than 4.8.20220815.130
  3. Check MMR service status
    Run systemctl status zoom-mmr or check if MMR-related processes/services are running
    Affected if MMR service is active and version is below 4.8.20220815.130
  4. Verify MMR configuration is in use
    Inspect configuration files in /opt/zoom or MMR configuration directories to confirm the Meeting Connector MMR component is enabled
    Affected if MMR is enabled in configuration and version is below the fixed release

A system is affected only if Zoom On-Premise Meeting Connector MMR is installed and running with a version lower than 4.8.20220815.130, as only those versions contain the improper access control flaw.

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.20220815.130 or later
Fixed in 4.8.20220815.130
Interim mitigation

Upgrade Zoom On-Premise Meeting Connector MMR to version 4.8.20220815.130 or later to remediate the access control flaw.

Recommended fix High confidence

4.8.20220815.130 or later

  1. 1. Identify the current version of Zoom On-Premise Meeting Connector MMR by checking the system administration interface or running the version check command
  2. 2. Download the fixed version (4.8.20220815.130 or later) from the official Zoom repository (explore.zoom.us)
  3. 3. Review the upgrade documentation provided by Zoom for the Meeting Connector MMR
  4. 4. Schedule a maintenance window as upgrades may require brief service interruption
  5. 5. Back up current configuration settings before proceeding
  6. 6. Apply the upgrade following Zoom's standard upgrade procedure for On-Premise Meeting Connector components
  7. 7. Verify the new version is installed correctly after upgrade completes
  8. 8. Test that authorized meeting joins work properly and unauthorized access is prevented

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28759 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