CVE-2021-26701 (High) detected in system.text.encodings.web.4.3.1.nupkg - autoclosed

[mend-bolt-for-github[bot]]

CVE-2021-26701 - High Severity Vulnerability

Vulnerable Library - system.text.encodings.web.4.3.1.nupkg

Provides types for encoding and escaping strings for use in JavaScript, HyperText Markup Language (H...

Library home page: https://api.nuget.org/packages/system.text.encodings.web.4.3.1.nupkg

Path to dependency file: /Tailspin.SpaceGame.Web.Tests/Tailspin.SpaceGame.Web.Tests.csproj

Path to vulnerable library: /home/wss-scanner/.nuget/packages/system.text.encodings.web/4.3.1/system.text.encodings.web.4.3.1.nupkg

Dependency Hierarchy: - microsoft.applicationinsights.aspnetcore.2.14.0.nupkg (Root Library) - microsoft.aspnetcore.hosting.1.0.2.nupkg - microsoft.aspnetcore.http.1.0.2.nupkg - microsoft.aspnetcore.webutilities.1.0.2.nupkg - :x: **system.text.encodings.web.4.3.1.nupkg** (Vulnerable Library)

Found in HEAD commit: f0bed70f8428d9b2c776ef5917b9e28e425c303c

Found in base branch: master

Vulnerability Details

.NET Core Remote Code Execution Vulnerability This CVE ID is unique from CVE-2021-24112.

Publish Date: 2021-02-25

URL: CVE-2021-26701

CVSS 3 Score Details (9.8)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/dotnet/announcements/issues/178

Release Date: 2021-02-25

Fix Resolution: System.Text.Encodings.Web - 4.5.1,4.7.2,5.0.1

---

Step up your Open Source Security Game with WhiteSource here

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #137

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #137