Immediately migrate to new .NET Core versions until EOS: Microsoft warns

All the developers who are using the.NET Core 3.1 LTS release are being asked by Microsoft to upgrade to the newest version of.NET Core before the LTS edition hits end of support (EOS) next month.

In a warning sent to the Windows message center, the firm urged users to upgrade to.NET 6 (LTS) or.NET 7 "as soon as feasible" before.NET Core 3.1 (LTS) hits EOS on December 13, 2022.

In July, Microsoft's Senior Program Manager in charge of.NET Core and.NET Native releases, Dominique Whittaker, issued a warning that the company will no longer provide technical support or maintenance upgrades after EOS.

"Upgrading to.NET 6 is strongly suggested. After the end of support, you will no longer receive.NET updates if your app is still using.NET Core 3.1. To keep your app maintained and receive.NET updates, you must upgrade it to.NET 6 or.NET 7, "According to Whittaker.

Apps built for.NET Core 3.1 will continue to function after the EOS is reached in less than a month, but they will be vulnerable to attacks that exploit any of the security vulnerabilities fixed in .NET Core 6 since its initial release in November 2021.

Whittaker further provided in-depth instructions on how developers and software makers may upgrade to.NET 6 (LTS) and refresh their respective IDEs.

_"Moving an application to .NET 6 might need addressing certain breaking changes. In order to ensure a successful relationship, we suggest you do the compatibility test"_ according to Microsoft's PM.

*Scheduling of.NET Framework releases (Microsoft)*

A new version of .NET,.NET 7, was launched on November 8 and will have 18 months of support, so users who wish to upgrade may do so.

In a blog post, the.NET team boasted that _".NET 7 provides your projects greater performance and new capabilities for C# 11/F# 7,.NET MAUI, ASP.NET Core/Blazor, Web APIs, WinForms, WPF, and more."_

_"With.NET 7, you can also easily containerize your.NET 7 applications, build up CI/CD workflows in GitHub actions, and attain cloud-native observability."_

Microsoft also warned developers in April to upgrade their programs from the.NET Framework 4.5.2, 4.6, and 4.6.1 to.NET Framework 4.6.2 or later by April 26. This was necessary to ensure continued access to security upgrades and technical support.

After the transition to SHA-2 signature, these three versions of the .NET Framework were deprecated because their digital certificates were generated using the outdated and vulnerable SHA-1 cryptographic hashing technique.

Immediately migrate to new .NET Core versions until EOS: Microsoft warns

Related threat feeds

Microsoft Warns of Legal Action After Researcher Publishes Defender & BitLocker Zero Day Exploits

148 Malicious npm Packages Used to Build a Browser Based DDoS Botnet

Pakistan Law Enforcement Agencies Targeted in Alleged Multi Group Cyber Espionage Operations