A remote code execution vulnerability exists in Microsoft Dynamics 365 for Finance and Operations (on-premises) version 10.0.11. An attacker who successfully exploited this vulnerability could gain remote code execution via server-side script execution on the victim server.
An authenticated attacker with privileges to import and export data could exploit this vulnerability by sending a specially crafted file to a vulnerable Dynamics server.
The security update addresses the vulnerability by correcting how Microsoft Dynamics 365 for Finance and Operations (on-premises) version 10.0.11 handles user input.
## Which versions are affected by CVE-2020-16857? It affects 1 product. Products: Microsoft Dynamics 365 for Finance and Operations. ## How do I fix CVE-2020-16857? No fix has been published for CVE-2020-16857 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-16857 being exploited? There is no known exploitation of CVE-2020-16857 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft Dynamics 365 for Finance and Operations - [CVE-2020-1182](https://insights.sbomify.com/CVE-2020-1182/): Microsoft Dynamics 365 for Finance and Operations (on-premises) Remote Code Execution Vulnerability (high 7.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-16857 and fix it if it is affected. What it is: CVE-2020-16857 is a high-severity code injection vulnerability in Microsoft Dynamics 365 for Finance and Operations, published on 11 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-16857 in the wild and no public exploit code. Affected product: Microsoft Dynamics 365 for Finance and Operations. 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-16857/ (Markdown: https://insights.sbomify.com/CVE-2020-16857/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-16857 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-16857 - OSV: https://osv.dev/vulnerability/CVE-2020-16857 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-16857/ Summaries are generated and may contain mistakes; the official description above is the record.