CVE-2021-34414
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 proxy page on the web portal for the Zoom on-premise Meeting Connector Controller before version 4.6.348.20201217, Zoom on-premise Meeting Connector MMR before version 4.6.348.20201217, Zoom on-premise Recording Connector before version 3.8.42.20200905, Zoom on-premise Virtual Room Connector before version 4.4.6620.20201110, 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 proxy configuration, which could lead to remote command injection on the on-premise image by a web portal administrator.
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 proxy configuration page in Zoom on-premise products (Meeting Connector Controller, Meeting Connector MMR, Recording Connector, Virtual Room Connector, and Virtual Room Connector Load Balancer) fails to validate input when updating proxy settings, allowing authenticated web portal administrators to inject arbitrary commands that execute on the underlying operating system.
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.348.20201217< 3.8.42.20200905< 4.4.6620.20201110< 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 productsCheck for installed Zoom products on the system. Look for Meeting Connector, Recording Connector, Virtual Room Connector, or Virtual Room Connector Load Balancer in installed software or services.Affected if Any of these Zoom on-premise products are installed on the system
-
Determine installed version of Zoom productCheck the version of the installed Zoom product. This is typically visible in the web admin portal about page, or via command line tools specific to each product (e.g., 'show version' for Virtual Room Connector).Affected if The installed version is lower than: Meeting Connector 4.6.348.20201217, Recording Connector 3.8.42.20200905, Virtual Room Connector 4.4.6620.20201110, or Virtual Room Connector Load Balancer 2.5.5495.20210326
-
Check web portal administrative accessVerify if the Zoom web admin portal is accessible and exposed. This is typically accessed via HTTPS on port 443 or 8443 for these products.Affected if The web administrative portal is accessible from network locations where untrusted users could potentially obtain admin credentials
-
Inspect proxy configuration for anomaliesReview the current proxy settings in the Zoom admin interface (Network Settings > Proxy). Look for unexpected characters, IP addresses, or shell command syntax in the proxy fields.Affected if The proxy configuration contains suspicious patterns such as shell metacharacters, unexpected IP addresses, or configurations not set by your organization
You are affected if you have any of these Zoom on-premise products installed with versions lower than the patched releases and the web admin portal is accessible to 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.42.202009054.4.6620.20201110
Upgrade to the patched versions (Meeting Connector: 4.6.348.20201217, Recording Connector: 3.8.42.20200905, Virtual Room Connector: 4.4.6620.20201110, Virtual Room Connector Load Balancer: 2.5.5495.20210326) or restrict web portal administrative access to trusted personnel only.
Meeting Connector >= 4.6.348.20201217, Recording Connector >= 3.8.42.20200905, Virtual Room Connector >= 4.4.6620.20201110, 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. Access the admin interface for each affected connector
- 3. Navigate to the network proxy configuration page
- 4. Before upgrading, backup current configuration settings
- 5. Upgrade Meeting Connector to version 4.6.348.20201217 or later
- 6. Upgrade Recording Connector to version 3.8.42.20200905 or later
- 7. Upgrade Virtual Room Connector to version 4.4.6620.20201110 or later
- 8. Upgrade Virtual Room Connector Load Balancer to version 2.5.5495.20210326 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34414 — 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-34414 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