dbcve.org
Visual StudioApplication · Microsoft

CVE-2023-33139

MEDIUM · 5.5 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to 15.8 / 15.9.55 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges Patch available

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 · unedited
Visual Studio Information Disclosure Vulnerability

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
How this class of weakness works · CWE-125

The code reads past the end (or before the start) of a buffer, returning memory that was never meant to be exposed. Attackers use it to leak secrets like keys or to defeat memory-protection defences. Remediation is validating indices and lengths before every read.

General guidance for the out-of-bounds read class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Visual StudioApplication
Affected:= 2015
Visual Studio 2017Application
Affected:>= 15.0, < 15.8>= 15.9, < 15.9.55
Visual Studio 2019Application
Affected:>= 16.0, <= 16.10>= 16.11, < 16.11.27
Visual Studio 2022Application
Affected:>= 17.0, < 17.0.22>= 17.2, < 17.2.16>= 17.4, < 17.4.8>= 17.6, < 17.6.3

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 · scoped
Upgrade available Upgrade to 15.8 / 15.9.55 / 16.11.27 or later
Fixed in 15.815.9.5516.11.27
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Upgrade to the minimum fixed version for your product line (VS 2017: 15.9.55, VS 2019: 16.11.27, VS 2022: 17.6.3 or later for the 17.6 channel)

  1. Identify the current Visual Studio version installed by opening Visual Studio, going to Help > About Microsoft Visual Studio
  2. Based on the installed version, determine the minimum fixed version required from the affected versions list
  3. For Visual Studio 2017: Upgrade to version 15.8 or later (first range), or 15.9.55 or later (second range)
  4. For Visual Studio 2019: Upgrade to version 16.11.27 or later
  5. For Visual Studio 2022: Upgrade to version 17.0.22, 17.2.16, 17.4.8, or 17.6.3 or later depending on the release channel (17.0, 17.2, 17.4, or 17.6 respectively)
  6. For Visual Studio 2015: Consider upgrading to a supported Visual Studio version as VS 2015 has no fixed version listed
  7. Download the desired version from visualstudio.microsoft.com/downloads/
  8. Run the installer and follow the prompts to complete the upgrade
Caveat Standard Visual Studio upgrade considerations apply - review release notes for your version for any breaking changes or required migrations

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33139 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-33139 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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