CVE-2018-1037

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.

Published: 2018-04-12 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-1037 is rated Moderate Risk (46.7/100): CVSS Medium severity, with high exploitation likelihood (EPSS 9.46%, 92th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-1037

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 12.32% 9.46% -2.86%
2 2025-11-18 9.46% 12.32% +2.86%
3 2025-09-28 — 9.46% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-1037

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2018-1037

Affected software / configurations for CVE-2018-1037

Vendor Product Version Raw CPE
microsoft visual_studio 2010 cpe:2.3:a:microsoft:visual_studio:2010:sp1:*:*:*:*:*:*
microsoft visual_studio 2012 cpe:2.3:a:microsoft:visual_studio:2012:update5:*:*:*:*:*:*
microsoft visual_studio 2013 cpe:2.3:a:microsoft:visual_studio:2013:update5:*:*:*:*:*:*
microsoft visual_studio 2015 cpe:2.3:a:microsoft:visual_studio:2015:update3:*:*:*:*:*:*
microsoft visual_studio 2017 cpe:2.3:a:microsoft:visual_studio:2017:*:*:*:*:*:*:*
microsoft visual_studio_2017 15.6.6 cpe:2.3:a:microsoft:visual_studio_2017:15.6.6:*:*:*:*:*:*:*
microsoft visual_studio_2017 15.7 cpe:2.3:a:microsoft:visual_studio_2017:15.7:*:preview:*:*:*:*:*

References for CVE-2018-1037

cvelogic Threat Intelligence