CVE-2020-0675 json
An information disclosure vulnerability exists in the Cryptography Next Generation (CNG) service when it fails to properly handle objects i…
published 2020-02-11 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-2168
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
An information disclosure vulnerability exists in the Cryptography Next Generation (CNG) service when it fails to properly handle objects in memory.To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application.The security update addresses the vulnerability by correcting how the service handles objects in memory., aka 'Windows Key Isolation Service Information Disclosure Vulnerability'. This CVE ID is unique from CVE-2020-0676, CVE-2020-0677, CVE-2020-0748, CVE-2020-0755, CVE-2020-0756.
Patch / fix
Exploit prediction
1.61% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Microsoft Windows
- Microsoft Windows Server
- Microsoft Windows 10 Version 1903 for 32-bit Systems
- Microsoft Windows 10 Version 1903 for x64-based Systems
- Microsoft Windows 10 Version 1903 for ARM64-based Systems
- Microsoft Windows Server, version 1903 (Server Core installation)
- Microsoft Windows 10 Version 1909 for 32-bit Systems
- Microsoft Windows 10 Version 1909 for x64-based Systems
- Microsoft Windows 10 Version 1909 for ARM64-based Systems
- Microsoft Windows Server, version 1909 (Server Core installation)
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2020-0675
patch, vendor-advisory
Sources
- CVE List CVE-2020-0675
- NVD CVE-2020-0675
Fencer Vulns 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.