CVE EVIDENCE REVIEW
ReviewHighEvidence review

CVE-2021-42277 evidence review

Microsoft Microsoft Visual Studio 2015 Update 3, Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8), Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)

CVE-2021-42277 affects Microsoft Microsoft Visual Studio 2015 Update 3, Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8), Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10). Review the CVSS score, exploitation signals, affected versions, remediation status, and linked source material before making a change.

Open CVE record
Evidence review

This record remains available for product and version identification, but it is not presented as a complete remediation procedure. Confirm the affected range and the supported fix in a direct vendor advisory before changing production systems.

ProductMicrosoft Microsoft Visual Studio 2015 Update 3, Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8), Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
Affected versions>= 14.0.0 < 27550.00, >= 15.9.0 < 15.9.41, >= 16.11.0 < 16.11.6, >= 16.0.0 < 16.7.21, >= 15.0.0 < 16.9.13, >= 10.0.10240.0 < 10.0.10240.19119, >= 10.0.14393.0 < 10.0.14393.4770, >= 10.0.17763.0 < 10.0.17763.2300, >= 10.0.0 < 10.0.17763.2300, >= 10.0.0 < 10.0.18363.1916, >= 10.0.0 < 10.0.19041.1348, >= 10.0.0 < 10.0.19042.1348, >= 10.0.0 < 10.0.19043.1348, >= 10.0.22000.0 < 10.0.22000.318, >= 10.0.20348.0 < 10.0.20348.350, 2015, >= 15.0 <= 15.9, >= 16.0 <= 16.11, 20h2, 21h1
Fixed versionsNo verified fixed-version field is available yet
Priority basisReview · CVSS 7.8 · EPSS 0.84%
01

Identify the product and installed version

Record whether Microsoft Microsoft Visual Studio 2015 Update 3, Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8), Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) is present, where it is installed, and which interfaces are exposed.

  • 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

Compare the affected range

Use the current record as an identification aid: >= 14.0.0 < 27550.00, >= 15.9.0 < 15.9.41, >= 16.11.0 < 16.11.6, >= 16.0.0 < 16.7.21, >= 15.0.0 < 16.9.13, >= 10.0.10240.0 < 10.0.10240.19119, >= 10.0.14393.0 < 10.0.14393.4770, >= 10.0.17763.0 < 10.0.17763.2300, >= 10.0.0 < 10.0.17763.2300, >= 10.0.0 < 10.0.18363.1916, >= 10.0.0 < 10.0.19041.1348, >= 10.0.0 < 10.0.19042.1348, >= 10.0.0 < 10.0.19043.1348, >= 10.0.22000.0 < 10.0.22000.318, >= 10.0.20348.0 < 10.0.20348.350, 2015, >= 15.0 <= 15.9, >= 16.0 <= 16.11, 20h2, 21h1. Resolve incomplete inventory results before deciding that an asset is unaffected.

03

Verify the authoritative remediation source

Open the linked source material and locate a direct vendor advisory for this CVE. Confirm the supported fixed release and product-specific update path before making a production change.

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.