Skip to content

YARP Denial of Service Vulnerability

High severity GitHub Reviewed Published Apr 12, 2022 in dotnet/yarp • Updated Jan 27, 2023

Package

nuget Yarp.ReverseProxy (NuGet)

Affected versions

< 1.0.1
= 1.1.0-rc.1.22152.1

Patched versions

1.0.1
1.1.0-rc.1.22211.2

Description

Impact

A denial of service vulnerability exists in how YARP processes input.

Patches

If you're using YARP 1.0.0, you should update to NuGet package version 1.0.1.
If you're using YARP 1.1.0-RC.1, you should update to NuGet package version 1.1.0-rc.1.22211.2.

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

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

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

References

CVE-2022-26924

References

@MihaZupan MihaZupan published to dotnet/yarp Apr 12, 2022
Published by the National Vulnerability Database Apr 15, 2022
Published to the GitHub Advisory Database Apr 22, 2022
Reviewed Apr 22, 2022
Last updated Jan 27, 2023

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

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(42nd percentile)

Weaknesses

No CWEs

CVE ID

CVE-2022-26924

GHSA ID

GHSA-8xc6-g8xw-h2c4

Source code

Credits

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