# CVE-2020-1018: Information disclosure in Dynamics 365 Business Central 2019 Spring Update

> Attackers can view masked field values in chart pages of Microsoft Dynamics Business Central/NAV on-premise, exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4hf4-8q97-rmrh

## What is CVE-2020-1018?

CVE-2020-1018 is a high-severity vulnerability in Microsoft Dynamics 365 Business Central 2019 Spring Update, published on 15 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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'.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2020-1018?

It affects 2 products.


Products: Microsoft Dynamics 365 Business Central, Microsoft Dynamics Nav.

## How do I fix CVE-2020-1018?

No fix has been published for CVE-2020-1018 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1018 being exploited?

There is no known exploitation of CVE-2020-1018 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Dynamics 365 Business Central 2019 Spring Update

- [CVE-2024-38225](https://insights.sbomify.com/CVE-2024-38225/): Microsoft Dynamics 365 Business Central Elevation of Privilege Vulnerability (high 8.8)
- [CVE-2024-35249](https://insights.sbomify.com/CVE-2024-35249/): Microsoft Dynamics 365 Business Central Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-41127](https://insights.sbomify.com/CVE-2022-41127/): Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central (On Premises) Remote Code Execution Vulnerability (high 8.5)
- [CVE-2024-43460](https://insights.sbomify.com/CVE-2024-43460/): Dynamics 365 Business Central Elevation of Privilege Vulnerability (high 8.1)
- [CVE-2024-21380](https://insights.sbomify.com/CVE-2024-21380/): Microsoft Dynamics Business Central/NAV Information Disclosure Vulnerability (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1018 and fix it if it is affected.

What it is: CVE-2020-1018 is a high-severity vulnerability in Microsoft Dynamics 365 Business Central 2019 Spring Update, published on 15 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1018 in the wild and no public exploit code.

Affected product: Microsoft Dynamics 365 Business Central 2019 Spring Update. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1018/ (Markdown: https://insights.sbomify.com/CVE-2020-1018/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1018
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1018
- OSV: https://osv.dev/vulnerability/CVE-2020-1018

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1018/
Summaries are generated and may contain mistakes; the official description above is the record.