Skip to content

YARP Denial of Service Vulnerability

High severity GitHub Reviewed Published Jun 22, 2023 in microsoft/reverse-proxy • Updated Jun 3, 2024

Package

nuget Yarp.ReverseProxy (NuGet)

Affected versions

<= 1.1.1
= 2.0.0

Patched versions

1.1.2
2.0.1

Description

Impact

A denial of service vulnerability exists in YARP.

Patches

If you're using YARP 1.x, you should update to NuGet package version 1.1.2.
If you're using YARP 2.0.0, you should update to NuGet package version 2.0.1.

You can do so by updating the PackageReference in your .csproj file

<ItemGroup>
- <PackageReference Include="Yarp.ReverseProxy" Version="2.0.0" />
- <PackageReference Include="Yarp.Telemetry.Consumption" Version="2.0.0" />
+ <PackageReference Include="Yarp.ReverseProxy" Version="2.0.1" />
+ <PackageReference Include="Yarp.Telemetry.Consumption" Version="2.0.1" />
</ItemGroup>

or by selecting 2.0.1 in the NuGet UI inside Visual Studio (Manage NuGet Packages / Updates)

References

CVE-2023-33141

References

@Tratcher Tratcher published to microsoft/reverse-proxy Jun 22, 2023
Published by the National Vulnerability Database Jun 23, 2023
Published to the GitHub Advisory Database Jun 23, 2023
Reviewed Jun 23, 2023
Last updated Jun 3, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.155%
(53rd percentile)

Weaknesses

CVE ID

CVE-2023-33141

GHSA ID

GHSA-jrjw-qgr2-wfcg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.