Visual Studio
CVE-2019-0537 — Microsoft Visual Studio Information Disclosure Vulnerability
Executive Summary
An information disclosure vulnerability exists when Visual Studio improperly discloses arbitrary file contents if the victim opens a malicious .vscontent file. An attacker who took advantage of this information disclosure could view arbitrary file contents from the computer where the victim launched Visual Studio. To take advantage of the vulnerability, an attacker would need to trick a user into opening a malicious .vscontent file using a vulnerable version of Visual Studio. An attacker would have no way to force a developer to produce this information disclosure. The security update addresses the vulnerability by correcting how Visual Studio loads .vscontent files.
Overview
5.5
CVSS MEDIUM
Important
MS Severity
Not Exploited
MS Exploit Status
Less Likely
MS Exploit Likelihood
CVSS Vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
ATTACK VECTOR
Local
ATTACK COMPLEXITY
Low
PRIVILEGES REQUIRED
None
USER INTERACTION
Required
SCOPE
Unchanged
EPSS Score
0.07614
probability of exploitation in the next 30 days
0.94014 percentile - updated 2026-08-14
View on FIRST.org
Affected Products
2 affected products
| Product | KB Article | Severity | Impact | Restart Required |
|---|---|---|---|---|
| Microsoft Visual Studio 2010 Service Pack 1 | 4476698 (Security Update) |
Important | Information Disclosure | Maybe |
| Microsoft Visual Studio 2012 Update 5 | 4476755 (Security Update) |
Important | Information Disclosure | Maybe |
Patches
2 patches
| Article | Type | Restart |
|---|---|---|
4476698 |
Security Update | Maybe |
4476755 |
Security Update | Maybe |
Exploits & PoC
No public exploit or PoC has been linked for this CVE yet. When available, references are sourced from public repositories and may be unverified or non-functional — review carefully before use.
Detection Rules
No public Sigma or Nuclei detection rule has been mapped to this CVE yet. Coverage is concentrated on exploited / high-profile vulnerabilities; check SigmaHQ for updates.
Acknowledgments
References
On This Page