ReviewHigh

CVE-2022-41119

Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8), Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10), Microsoft Visual Studio 2022 version 17.0

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

CVSS
7.8
EPSS
0.80%
53.9% percentile
CISA KEV
Not listed
Published
2022.11.10
PRIORITY ASSESSMENT

Review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.80%
Technical severityCVSS 7.8

Vulnerability overview

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

Affected product and versions

Product
Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8), Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10), Microsoft Visual Studio 2022 version 17.0
Affected versions
>= 15.9.0 < 15.9.51, >= 16.11.0 < 16.11.21, >= 17.0.0 < 17.0.16, >= 17.2.0 < 17.2.10, >= 17.0.0 < 17.3.7, >= 15.0 <= 15.9, >= 16.0 <= 16.11, 17.0, 17.2, 17.3
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8), Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10), Microsoft Visual Studio 2022 version 17.0 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CWE
Not available