[repo] Mitigate vulnerabilities in System.Text.Json 8.0.4 package #5891
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Details
We just bumped STJ to 8.0.4 for
net8.0
targets but a new vulnerability was published today.This PR bumps STJ to
8.0.5
fornet8.0
targets.Unlike the previous CVE,
net6.0
is also impacted and a new version6.0.10
was published fornet6.0
. No action is being taken fornet6.0
. Because we have already removednet6.0
targets for1.10.0
(net6.0
is going out of support). Users upgrading to1.10.0
and running onnet6.0
will fallback to thenetstandard2.0
target which uses4.7.2
with no known vulnerabilities. We could hot-patch older versions, but this vulnerability deals with de-serialization of untrusted user input which we don't do in the components using STJ. Treating this as a low severity issue where a hot-patch is not needed. If this changes or new information comes to light we can do a patch, just not planning to do one at this time.Today:
1.9.0 stable:
1.10.0-beta.1:
Going forward:
1.9.0 stable:
No hot patch currently planned. The vulnerability is about deserialization of untrusted input which neither ConsoleExporter nor ZipkinExporter is susceptible to. I'm approaching this as a low severity issue. If we determine there is a higher severity we will do a hot patch for 1.9.0, possibly other releases.
Next release of 1.10.0:
Merge requirement checklist