CVE REMEDIATION GUIDE
Priority reviewHighResearch in progress

CVE-2021-34535 remediation guide

Microsoft Remote Desktop client for Windows Desktop, Windows 10 Version 1507, Windows 10 Version 1607

CVE-2021-34535 affects Microsoft Remote Desktop client for Windows Desktop, Windows 10 Version 1507, Windows 10 Version 1607. Review the CVSS score, exploitation signals, affected versions, remediation status, and linked source material before making a change.

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductMicrosoft Remote Desktop client for Windows Desktop, Windows 10 Version 1507, Windows 10 Version 1607
Affected versions>= 1.2.0.0 < publication, >= 10.0.10240.0 < 10.0.10240.19022, >= 10.0.14393.0 < 10.0.14393.4583, >= 10.0.17763.0 < 10.0.17763.2114, >= 10.0.0 < 10.0.17763.2114, >= 10.0.0 < 10.0.18363.1734, >= 10.0.0 < 10.0.19041.1165, >= 10.0.0 < 10.0.19042.1165, >= 10.0.0 < 10.0.19043.1165, >= 6.1.0 < 6.1.7601.25685, >= 6.3.0 < 6.3.9600.20094, >= 6.1.7601.0 < 6.1.7601.25685, >= 6.2.9200.0 < 6.2.9200.23435, >= 6.3.9600.0 < 6.3.9600.20094, 20h2, 21h1, 1607, 1809, 1909, 2004
Fixed versionsNo verified fixed-version field is available yet
Priority basisPriority · CVSS 8.8 · EPSS 20.4%
01

Identify the affected asset

Confirm whether Microsoft Remote Desktop client for Windows Desktop, Windows 10 Version 1507, Windows 10 Version 1607 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 1.2.0.0 < publication, >= 10.0.10240.0 < 10.0.10240.19022, >= 10.0.14393.0 < 10.0.14393.4583, >= 10.0.17763.0 < 10.0.17763.2114, >= 10.0.0 < 10.0.17763.2114, >= 10.0.0 < 10.0.18363.1734, >= 10.0.0 < 10.0.19041.1165, >= 10.0.0 < 10.0.19042.1165, >= 10.0.0 < 10.0.19043.1165, >= 6.1.0 < 6.1.7601.25685, >= 6.3.0 < 6.3.9600.20094, >= 6.1.7601.0 < 6.1.7601.25685, >= 6.2.9200.0 < 6.2.9200.23435, >= 6.3.9600.0 < 6.3.9600.20094, 20h2, 21h1, 1607, 1809, 1909, 2004. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: No verified fixed-version field is available yet. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.