You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to dependency file: /swagger-client/csharp/src/IO.Swagger/IO.Swagger.nuspec
Path to vulnerable library: /home/wss-scanner/.nuget/packages/restsharp/111.4.1/restsharp.111.4.1.nupkg,/home/wss-scanner/.nuget/packages/restsharp/111.4.1/restsharp.111.4.1.nupkg,/swagger-client/csharp/src/IO.Swagger.Test/packages/RestSharp.111.4.1/RestSharp.111.4.1.nupkg
RestSharp is a Simple REST and HTTP API Client for .NET. The second argument to RestRequest.AddHeader (the header value) is vulnerable to CRLF injection. The same applies to RestRequest.AddOrUpdateHeader and RestClient.AddDefaultHeader. The way HTTP headers are added to a request is via the HttpHeaders.TryAddWithoutValidation method which does not check for CRLF characters in the header value. This means that any headers from a RestSharp.RequestHeaders object are added to the request in such a way that they are vulnerable to CRLF-injection. In general, CRLF-injection into a HTTP header (when using HTTP/1.1) means that one can inject additional HTTP headers or smuggle whole HTTP requests. If an application using the RestSharp library passes a user-controllable value through to a header, then that application becomes vulnerable to CRLF-injection. This is not necessarily a security issue for a command line application like the one above, but if such code were present in a web application then it becomes vulnerable to request splitting (as shown in the PoC) and thus Server Side Request Forgery. Strictly speaking this is a potential vulnerability in applications using RestSharp, not in RestSharp itself, but I would argue that at the very least there needs to be a warning about this behaviour in the RestSharp documentation. RestSharp has addressed this issue in version 112.0.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.
CVE-2024-45302 - Medium Severity Vulnerability
Vulnerable Libraries - RestSharp-111.4.1.dll, RestSharp-111.4.1.dll, restsharp.111.4.1.nupkg, RestSharp-111.4.1.dll, RestSharp-111.4.1.dll, RestSharp-111.4.1.dll, RestSharp-111.4.1.dll
RestSharp-111.4.1.dll
RestSharp
Library home page: https://api.nuget.org/packages/restsharp.111.4.1.nupkg
Path to vulnerable library: /swagger-client/csharp/src/IO.Swagger.Test/packages/RestSharp.111.4.1/lib/netstandard2.0/RestSharp.dll
Dependency Hierarchy:
RestSharp-111.4.1.dll
RestSharp
Library home page: https://api.nuget.org/packages/restsharp.111.4.1.nupkg
Path to vulnerable library: /swagger-client/csharp/src/IO.Swagger.Test/packages/RestSharp.111.4.1/lib/net471/RestSharp.dll
Dependency Hierarchy:
restsharp.111.4.1.nupkg
Simple REST and HTTP API Client
Library home page: https://api.nuget.org/packages/restsharp.111.4.1.nupkg
Path to dependency file: /swagger-client/csharp/src/IO.Swagger/IO.Swagger.nuspec
Path to vulnerable library: /home/wss-scanner/.nuget/packages/restsharp/111.4.1/restsharp.111.4.1.nupkg,/home/wss-scanner/.nuget/packages/restsharp/111.4.1/restsharp.111.4.1.nupkg,/swagger-client/csharp/src/IO.Swagger.Test/packages/RestSharp.111.4.1/RestSharp.111.4.1.nupkg
Dependency Hierarchy:
RestSharp-111.4.1.dll
RestSharp
Library home page: https://api.nuget.org/packages/restsharp.111.4.1.nupkg
Path to vulnerable library: /swagger-client/csharp/src/IO.Swagger.Test/packages/RestSharp.111.4.1/lib/net7.0/RestSharp.dll
Dependency Hierarchy:
RestSharp-111.4.1.dll
RestSharp
Library home page: https://api.nuget.org/packages/restsharp.111.4.1.nupkg
Path to vulnerable library: /swagger-client/csharp/src/IO.Swagger.Test/packages/RestSharp.111.4.1/lib/net8.0/RestSharp.dll
Dependency Hierarchy:
RestSharp-111.4.1.dll
RestSharp
Library home page: https://api.nuget.org/packages/restsharp.111.4.1.nupkg
Path to vulnerable library: /swagger-client/csharp/src/IO.Swagger.Test/packages/RestSharp.111.4.1/lib/net6.0/RestSharp.dll
Dependency Hierarchy:
RestSharp-111.4.1.dll
RestSharp
Library home page: https://api.nuget.org/packages/restsharp.111.4.1.nupkg
Path to vulnerable library: /swagger-client/csharp/src/IO.Swagger.Test/packages/RestSharp.111.4.1/lib/net48/RestSharp.dll
Dependency Hierarchy:
Found in HEAD commit: 0879348474e22463e77dc76ba5e5f7e6300a2b6c
Found in base branch: master
Vulnerability Details
RestSharp is a Simple REST and HTTP API Client for .NET. The second argument to
RestRequest.AddHeader
(the header value) is vulnerable to CRLF injection. The same applies toRestRequest.AddOrUpdateHeader
andRestClient.AddDefaultHeader
. The way HTTP headers are added to a request is via theHttpHeaders.TryAddWithoutValidation
method which does not check for CRLF characters in the header value. This means that any headers from aRestSharp.RequestHeaders
object are added to the request in such a way that they are vulnerable to CRLF-injection. In general, CRLF-injection into a HTTP header (when using HTTP/1.1) means that one can inject additional HTTP headers or smuggle whole HTTP requests. If an application using the RestSharp library passes a user-controllable value through to a header, then that application becomes vulnerable to CRLF-injection. This is not necessarily a security issue for a command line application like the one above, but if such code were present in a web application then it becomes vulnerable to request splitting (as shown in the PoC) and thus Server Side Request Forgery. Strictly speaking this is a potential vulnerability in applications using RestSharp, not in RestSharp itself, but I would argue that at the very least there needs to be a warning about this behaviour in the RestSharp documentation. RestSharp has addressed this issue in version 112.0.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.Publish Date: 2024-08-29
URL: CVE-2024-45302
CVSS 3 Score Details (6.1)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-4rr6-2v9v-wcpc
Release Date: 2024-08-29
Fix Resolution: RestSharp - 112.0.0
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: