CVE-2020-1018 json
An information disclosure vulnerability exists when Microsoft Dynamics Business Central/NAV on-premise does not properly hide the value of…
published 6y ago modified 4mo ago also EUVD-2020-11914
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.3%
- EPSS 6.3% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
An information disclosure vulnerability exists when Microsoft Dynamics Business Central/NAV on-premise does not properly hide the value of a masked field when showing the records as a chart page.The attacker who successfully exploited the vulnerability could see the information that are in a masked field.The security update addresses the vulnerability by updating the rendering engine the Windows client to properly detect masked fields and render the content as masked., aka 'Microsoft Dynamics Business Central/NAV Information Disclosure'.
Patch / fix
Is CVE-2020-1018 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
6.31% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Microsoft Microsoft Dynamics NAV 2016
- Microsoft Microsoft Dynamics NAV 2017
- Microsoft Microsoft Dynamics NAV 2018
- Microsoft Microsoft Dynamics NAV 2015
- Microsoft Microsoft Dynamics 365 BC On Premise
- Microsoft Dynamics 365 Business Central 2019 Spring Update
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2020-1018
patch, vendor-advisory
Sources
- CVE List CVE-2020-1018
- NVD CVE-2020-1018
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.