An information disclosure vulnerability exists when the Windows GDI component improperly discloses the contents of its memory, aka 'Windows…

published 2019-03-05 7y ago modified 2026-06-17 4mo ago also EUVD-2019-1379

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 7.7%; EPSS 7.7% chance of exploitation in 30 days, percentile 94%
public exploits: 0; none known

An information disclosure vulnerability exists when the Windows GDI component improperly discloses the contents of its memory, aka 'Windows GDI Information Disclosure Vulnerability'. This CVE ID is unique from CVE-2019-0602, CVE-2019-0616, CVE-2019-0619, CVE-2019-0660, CVE-2019-0664.

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0615 advisory

Is CVE-2019-0615 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

7.71% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

Microsoft Windows
Microsoft Windows Server

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2019-0615
patch, vendor-advisory
securityfocus.com /bid/106860
vdb-entry, third-party-advisory

Sources

CVE List CVE-2019-0615
NVD CVE-2019-0615

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.