Magnus Rahl
Jul 1, 2022
  1981
(1 votes)

Addressing vulnerability in Newtonsoft.Json

We have received questions about the recently disclosed vulnerability in Newtonsoft.Json prior to version 13.0.1. Having the dependency doesn't mean you're automatically vulnerable, but since several of our packages depend on Newtonsoft.Json, DXP solutions (including custom code) are theoretically vulnerable. 

The vulnerability was disclosed after 5 PM June 22, and came to our knowledge the next day, June 23. We started investigating immediately and had verified remediation steps early June 24, in the hands of our support teams to respond to customers/partners reaching out about this.

Publishing this information more broadly now is of course a tradeoff between reaching more of our customers and partners, and drawing attention to the vulnerability. However, because Newtonsoft.Json is the #1 used .NET library, it is well known that we are a .NET solution, and the dependency can be seen in public information on Nuget, we decided to go ahead and publish this information together with the remediation.

Remediation

Newer versions like CMS 12, Commerce 14 and Find 14 are not vulnerable since they require Newtonsoft.Json 13.0.1. 

On slightly older solutions, you can simply update Newtonsoft.Json in your solution to version 13.0.1 or later, for example using Nuget Package Manager.

On yet older versions (earlier verisons of CMS 11, Commerce 13, Find 13) you may run into a version restriction. You can override this version restriction by updating the package using the Package Manager Console and supplying the -IgnoreDepencencies flag:

Update-Package Newtonsoft.Json -Version 13.0.1 -IgnoreDependencies

Or simply edit the packages.config file to set the version of Newtonsoft.Json to 13.0.1.

We have gone back quite a few versions and verified that forcing the version restriction does not have any negative side-effects. We have done this as far back as EPiServer.Commerce 13.14.0, EPiServer.CMS 11.14.0 (EPiServer.CMS.UI 11.23.1), EPiServer.Find 13.2.6, EPiServer.Find.Commerce 11.2.0 and EPiServer.ContentDeliveryApi 2.21.0.

If you have any questions, please reach out to support.

Jul 01, 2022

Comments

Please login to comment.
Latest blogs
Official List property support

Introduction Until now users were able to store list properties in three ways: Store simple types (int, string, DateTime, double) as native...

Bartosz Sekula | Mar 28, 2023

New dashboard implemented in CMS UI 12.18.0

As part of the CMS UI 12.18.0 release , a new dashboard has been added as a ‘one stop shop’ to enable editors to access all of their content items,...

Matthew Slim | Mar 28, 2023

How to Merge Anonymous Carts When a Customer Logs In with Optimizely Commerce 14

In e-commerce, it is common for users to browse a site anonymously, adding items to their cart without creating an account. Later, when the user...

Francisco Quintanilla | Mar 27, 2023

How to Write an xUnit Test to Verify Unique Content Type Guids in Content Management

When developing an Optimizely CMS solution, it is important to ensure that each content type has a unique GUID. If two or more content types share...

Minesh Shah (Netcel) | Mar 27, 2023