CVE-2021-34417
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.365.20210703, Zoom On-Premise Meeting Connector MMR before version 4.6.365.20210703, Zoom On-Premise Recording Connector before version 3.8.45.20210703, Zoom On-Premise Virtual Room Connector before version 4.4.6868.20210703, and Zoom On-Premise Virtual Room Connector Load Balancer before version 2.5.5496.20210703 fails to validate input sent in requests to set the network proxy password. This could lead to remote command injection 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 page in Zoom On-Premise products (Meeting Connector Controller, MMR, Recording Connector, Virtual Room Connector, and Load Balancer) fails to validate input in the proxy password field, allowing an authenticated web portal administrator to inject arbitrary commands through unsanitized input.
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.365.20210703< 4.6.365.20210703< 3.8.45.20210703< 4.4.6868.20210703< 2.5.5496.20210703CVSS 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 productsLocate Zoom On-Premise components on the system: Meeting Connector Controller (MCC), Meeting Connector MMR, Recording Connector, Virtual Room Connector, or Load Balancer. Check installation directories or package inventories for these services.Affected if Any of the listed Zoom On-Premise components are present on the system
-
Check product versionFor each installed Zoom On-Premise component, retrieve the version number. This is typically available in the product UI under Help > About, in the admin dashboard, or via command-line tools specific to each component (e.g., 'version' command or config files).Affected if The installed version is below 4.6.365.20210703 for Connectors/MMR, below 3.8.45.20210703 for Recording Connector, or below 4.4.6868.20210703 for Virtual Room Connector/Load Balancer
-
Verify web portal accessibilityConfirm the Zoom web management portal is accessible. The vulnerability requires an authenticated administrator session to the web portal to inject commands through the proxy password field.Affected if The web management portal is exposed and reachable with administrator credentials
-
Check proxy configuration pageNavigate to the network proxy settings page in the Zoom On-Premise admin interface. The vulnerable input field is the proxy password field in the proxy configuration section.Affected if The proxy configuration page exists and accepts input in the password field (indicating the vulnerable code path is present)
A user is affected if they run any of the listed Zoom On-Premise products at a version below the specified thresholds AND have the web management portal accessible, as the command injection occurs through the proxy password field in the admin interface.
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.5496.202107033.8.45.202107034.4.6868.20210703
Update all affected Zoom On-Premise components to versions 4.6.365.20210703 or later for Connectors, 3.8.45.20210703 for Recording Connector, and 4.4.6868.20210703 or later for Virtual Room Connector products.
Meeting Connector Controller/MMR: 4.6.365.20210703 | Recording Connector: 3.8.45.20210703 | Virtual Room Connector: 4.4.6868.20210703 | Virtual Room Connector Load Balancer: 2.5.5496.20210703
- Identify which Zoom On-Premise components are deployed in your environment from the list: Meeting Connector Controller, Meeting Connector MMR, Recording Connector, Virtual Room Connector, or Virtual Room Connector Load Balancer
- For Zoom On-Premise Meeting Connector Controller: upgrade to version 4.6.365.20210703 or later
- For Zoom On-Premise Meeting Connector MMR: upgrade to version 4.6.365.20210703 or later
- For Zoom On-Premise Recording Connector: upgrade to version 3.8.45.20210703 or later
- For Zoom On-Premise Virtual Room Connector: upgrade to version 4.4.6868.20210703 or later
- For Zoom On-Premise Virtual Room Connector Load Balancer: upgrade to version 2.5.5496.20210703 or later
- After upgrading, verify the network proxy settings page no longer accepts unsanitized input and that the password field properly validates and sanitizes all input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34417 — 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-34417 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