Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency RestSharp to v112 [SECURITY] - autoclosed #417

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 29, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
RestSharp (source) 111.4.1 -> 112.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-45302

Summary

The second argument to RestRequest.AddHeader (the header value) is vulnerable to CRLF injection. The same applies to RestRequest.AddOrUpdateHeader and RestClient.AddDefaultHeader.

Details

The way HTTP headers are added to a request is via the HttpHeaders.TryAddWithoutValidation method: https://github.com/restsharp/RestSharp/blob/777bf194ec2d14271e7807cc704e73ec18fcaf7e/src/RestSharp/Request/HttpRequestMessageExtensions.cs#L32 This method 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.

PoC

The below example code creates a console app that takes one command line variable "api key" and then makes a request to some status page with the provided key inserted in the "Authorization" header:

using RestSharp;

class Program
{
    static async Task Main(string[] args)
    {
        // Usage: dotnet run <api key>
        var key = args[0];
        var options = new RestClientOptions("http://insert.some.site.here");
        var client = new RestClient(options);
        var request = new RestRequest("/status", Method.Get).AddHeader("Authorization", key);
        var response = await client.ExecuteAsync(request);
        Console.WriteLine($"Status: {response.StatusCode}");
        Console.WriteLine($"Response: {response.Content}");
    }
}

This application is now vulnerable to CRLF-injection, and can thus be abused to for example perform request splitting and thus server side request forgery (SSRF):

anonymous@ubuntu-sofia-672448:~$ dotnet RestSharp-cli.dll $'test\r\nUser-Agent: injected header!\r\n\r\nGET /smuggled HTTP/1.1\r\nHost: insert.some.site.here'
Status: OK
Response: <html></html>

The application intends to send a single request of the form:

GET /status HTTP/1.1
Host: insert.some.site.here
Authorization: <api key>
User-Agent: RestSharp/111.4.1.0
Accept: application/json, text/json, text/x-json, text/javascript, application/xml, text/xml
Accept-Encoding: gzip, deflate, br

But as the application is vulnerable to CRLF injection the above command will instead result in the following two requests being sent:

GET /status HTTP/1.1
Host: insert.some.site.here
Authorization: test
User-Agent: injected header!

and

GET /smuggled HTTP/1.1
Host: insert.some.site.here
User-Agent: RestSharp/111.4.1.0
Accept: application/json, text/json, text/x-json, text/javascript, application/xml, text/xml
Accept-Encoding: gzip, deflate, br

This can be confirmed by checking the access logs on the server where these commands were run (with insert.some.site.here pointing to localhost):

anonymous@ubuntu-sofia-672448:~$ sudo tail /var/log/apache2/access.log
127.0.0.1 - - [29/Aug/2024:11:41:11 +0000] "GET /status HTTP/1.1" 200 240 "-" "injected header!"
127.0.0.1 - - [29/Aug/2024:11:41:11 +0000] "GET /smuggled HTTP/1.1" 404 436 "-" "RestSharp/111.4.1.0"

Impact

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.


Release Notes

restsharp/RestSharp (RestSharp)

v112.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: restsharp/RestSharp@111.4.1...112.0.0


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

coderabbitai bot commented Aug 29, 2024

Walkthrough

The changes involve updating the RestSharp package version from 111.4.1 to 112.0.0 across multiple project files. This update may introduce new features, improvements, or bug fixes that could affect how HTTP requests are managed within the applications. The specific implications of this version change on each codebase's functionality are not detailed in the updates.

Changes

Files Change Summary
jobs/RabbitMQCheck/RabbitMQCheck.csproj, nuget packages/AigSmsHook/AigSmsHook.csproj, nuget packages/Planar.Client/Planar.Client.csproj, src/Jobs/RestJob/RestJob.csproj, src/Planar.CLI/Planar.CLI.csproj Updated RestSharp package version from 111.4.1 to 112.0.0.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant RestSharp
    participant Server

    Client->>RestSharp: Send HTTP Request
    RestSharp->>Server: Forward Request
    Server-->>RestSharp: Send Response
    RestSharp-->>Client: Return Response
Loading

Poem

🐰 In fields of code, I hop with glee,
A new RestSharp version, oh what a spree!
With features fresh and bugs now gone,
I’ll send my requests, from dusk till dawn.
Hooray for updates, let’s celebrate,
A happy rabbit, I can’t wait! 🥕


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

sonarcloud bot commented Aug 29, 2024

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4e5090e and ca17202.

Files selected for processing (5)
  • generic jobs/RabbitMQCheck/RabbitMQCheck.csproj (1 hunks)
  • nuget packages/AigSmsHook/AigSmsHook.csproj (1 hunks)
  • nuget packages/Planar.Client/Planar.Client.csproj (1 hunks)
  • src/Jobs/RestJob/RestJob.csproj (1 hunks)
  • src/Planar.CLI/Planar.CLI.csproj (1 hunks)
Additional comments not posted (5)
nuget packages/AigSmsHook/AigSmsHook.csproj (1)

11-11: LGTM! But verify the package usage in the codebase.

The update to RestSharp version 112.0.0 is necessary to address the security vulnerability GHSA-4rr6-2v9v-wcpc. Ensure that the new version does not introduce breaking changes in the codebase.

The code changes are approved.

Run the following script to verify the package usage:

src/Jobs/RestJob/RestJob.csproj (1)

25-25: LGTM! But verify the package usage in the codebase.

The update to RestSharp version 112.0.0 is necessary to address the security vulnerability GHSA-4rr6-2v9v-wcpc. Ensure that the new version does not introduce breaking changes in the codebase.

The code changes are approved.

Run the following script to verify the package usage:

generic jobs/RabbitMQCheck/RabbitMQCheck.csproj (1)

15-15: LGTM! But verify the package usage in the codebase.

The update to RestSharp version 112.0.0 is necessary to address the security vulnerability GHSA-4rr6-2v9v-wcpc. Ensure that the new version does not introduce breaking changes in the codebase.

The code changes are approved.

Run the following script to verify the package usage:

nuget packages/Planar.Client/Planar.Client.csproj (1)

35-35: LGTM! But verify for breaking changes.

The update to RestSharp version 112.0.0 addresses a security vulnerability related to CRLF injection. Ensure that the new version does not introduce breaking changes that could affect the application's functionality.

The code changes are approved.

Run the following script to verify for breaking changes:

src/Planar.CLI/Planar.CLI.csproj (1)

47-47: LGTM! But verify for breaking changes.

The update to RestSharp version 112.0.0 addresses a security vulnerability related to CRLF injection. Ensure that the new version does not introduce breaking changes that could affect the application's functionality.

The code changes are approved.

Run the following script to verify for breaking changes:

@renovate renovate bot changed the title Update dependency RestSharp to v112 [SECURITY] Update dependency RestSharp to v112 [SECURITY] - autoclosed Sep 5, 2024
@renovate renovate bot closed this Sep 5, 2024
@renovate renovate bot deleted the renovate/nuget-restsharp-vulnerability branch September 5, 2024 14:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants