CVE-2020-1391 json
An information disclosure vulnerability exists when the Windows Agent Activation Runtime (AarSvc) fails to properly handle objects in memor…
published 6y ago modified 4mo ago also EUVD-2020-12267
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
An information disclosure vulnerability exists when the Windows Agent Activation Runtime (AarSvc) fails to properly handle objects in memory, aka 'Windows Agent Activation Runtime Information Disclosure Vulnerability'.
Patch / fix
Is CVE-2020-1391 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 FencerExploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 10 Version 2004 for 32-bit Systems
- Microsoft Windows 10 Version 2004 for ARM64-based Systems
- Microsoft Windows 10 Version 2004 for x64-based Systems
- Microsoft Windows Server, version 2004 (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)
- 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)
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2020-1391
patch, vendor-advisory
Sources
- CVE List CVE-2020-1391
- NVD CVE-2020-1391
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.