Skip to main content

Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central (On Premises) Remote Code Execution Vulnerability

Introduction: 

On 11th January 2023, Microsoft announced a vulnerability in NAV 2016, NAV 2017, and Business Central (On-Premise), and the fixes are shared below.


Pre-requisites: 

  • Used / Implemented NAV 2016/2017 or Business Central On-Premise

Books & References: 


Details: 

NOTE:  THIS VULNERABILITY IS CRITICAL IN NATURE.

1. Vulnerability:
Microsoft identified Remote Code Execution Vulnerabilities in NAV 2016, NAV2017, and Business Central On-Premise. While the fixes are released below.
Versions of NAV and Business Central were affected as follows -




2. Resolution:
If you are using Business Central Online, you are free


For versions that are out of mainstream support can you visit  CVE-2022-41127: Download localized DVDs for Dynamics NAV 2016 and NAV 2017 - Dynamics 365 Business Central Community or download from the list below.

Dynamics NAV 2016 (version 9.0)


Dynamics NAV 2017 (version 10.0)


Conclusion:

Please note that the vulnerability is critical in nature and will affect your NAV/BC installation as well. Download and install the latest security patches as soon as possible.
Labels:

Comments

Post a Comment

Let me know your comments below. I'll try my best to answer your comment

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta
Post a Comment
Read more

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr
7 comments
Read more

Business Central Environment Blinking after update to v20

Introduction: Business Central Updates after updating to version 20.x, there is a common problem which is observed. The Business Central environment starts blinking as per the video below - Pre- requisites : Business Central Online  v20 Demonstration: 1. Restart the Business Central Environment: Go to Business Central Admin Center > Select the Environment >Sessions > Restart Environment. 2. Ensure that your URL contains Tenant ID: When you login into the Business Central Environment, make sure that your links are in the following formats Sandbox : https://businesscentral.dynamics.com/<SandboxEnvironmentName>/?sandbox=true Production : https://businesscentral.dynamics.com/<ProductionEnvironmentName>/ If you URL like https://businesscentral.dynamics.com/SandboxName or any other format without Tenant ID, chances are that you will end up with the issue. Also, you can login through Admin Center URL -  Connect from URL in BC Admin Center 3. Check the status if the insta
Post a Comment
Read more