CVE-2021-34416
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 · uneditedThe network address administrative settings web portal for the Zoom on-premise Meeting Connector before version 4.6.360.20210325, Zoom on-premise Meeting Connector MMR before version 4.6.360.20210325, Zoom on-premise Recording Connector before version 3.8.44.20210326, Zoom on-premise Virtual Room Connector before version 4.4.6752.20210326, and Zoom on-premise Virtual Room Connector Load Balancer before version 2.5.5495.20210326 fails to validate input sent in requests to update the network configuration, which could lead to remote command injection on the on-premise image by the web portal administrators.
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 confidenceThe network address administrative settings web portal in multiple Zoom on-premise products (Meeting Connector, Recording Connector, Virtual Room Connector, and Load Balancer) fails to validate input in requests to update network configuration, allowing authenticated web portal administrators to inject arbitrary OS commands.
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< 4.6.360.20210325< 3.8.44.20210326< 4.4.6752.20210326< 2.5.5495.20210326CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Zoom on-premise productsLocate and inventory Zoom Meeting Connector, Recording Connector, Virtual Room Connector, or Virtual Room Connector Load Balancer installations on your network. Check running services, installed applications, or documentation for presence of these components.Affected if Any of these four Zoom on-premise products are present in the environment
-
Determine installed version of Zoom productAccess the administrative web portal of the installed Zoom product and navigate to the about or system information page to obtain the version number. Alternatively, check the software installation directory or package manager for version metadata.Affected if The installed version falls below 4.6.360.20210325 for Meeting Connector, 3.8.44.20210326 for Recording Connector, 4.4.6752.20210326 for Virtual Room Connector, or 2.5.5495.20210326 for Load Balancer
-
Verify web portal administrative interface is enabledConfirm that the network address administrative settings web portal is accessible. This is typically accessible via HTTPS on port 443 or 8443 for the administrative interface.Affected if The administrative web portal is exposed and accessible to users with administrator credentials
-
Check for unauthorized administrative accounts or commandsReview web server logs, system logs, and audit trails for requests to network configuration endpoints that may contain command injection patterns, unexpected network settings changes, or new administrative user accounts.Affected if Logs show unexpected network configuration changes, suspicious command strings in web requests, or unauthorized administrator activity
You are affected if any Zoom Meeting Connector, Recording Connector, Virtual Room Connector, or Load Balancer is running with a version below the thresholds AND the administrative web portal is accessible to authenticated administrators.
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.
dbcve · scoped2.5.5495.202103263.8.44.202103264.4.6752.20210326
Upgrade affected Zoom on-premise products to version 4.6.360.20210325 or later for Meeting Connectors, 3.8.44.20210326 or later for Recording Connectors, 4.4.6752.20210326 or later for Virtual Room Connectors, and 2.5.5495.20210326 or later for Load Balancers.
Meeting Connector >= 4.6.360.20210325 | Recording Connector >= 3.8.44.20210326 | Virtual Room Connector >= 4.4.6752.20210326 | Virtual Room Connector Load Balancer >= 2.5.5495.20210326
- 1. Identify which Zoom on-premise connectors are deployed in your environment (Meeting Connector, Recording Connector, Virtual Room Connector, or Virtual Room Connector Load Balancer)
- 2. Check the current version of each deployed connector by accessing the administrative web portal
- 3. Download the fixed version from Zoom's official portal (explore.zoom.us) or your Zoom support channel
- 4. For Meeting Connector: upgrade to version 4.6.360.20210325 or later
- 5. For Recording Connector: upgrade to version 3.8.44.20210326 or later
- 6. For Virtual Room Connector: upgrade to version 4.4.6752.20210326 or later
- 7. For Virtual Room Connector Load Balancer: upgrade to version 2.5.5495.20210326 or later
- 8. After upgrading, verify the network address administrative settings web portal input validation is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34416 — 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-2021-34416 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