-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore(deps): update dependency restsharp to v112 [security] #863
Open
marvin-serp-bot
wants to merge
1
commit into
main
Choose a base branch
from
upgrade/nuget-restsharp-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✒️ PR Title Commitlint - ✔️ Lint success! |
marvin-serp-bot
force-pushed
the
upgrade/nuget-restsharp-vulnerability
branch
from
October 9, 2024 23:06
c56f43c
to
976ff1a
Compare
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security]
chore(deps): update dependency restsharp to v112 [security] - autoclosed
Oct 10, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security] - autoclosed
chore(deps): update dependency restsharp to v112 [security]
Oct 10, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security]
chore(deps): update dependency restsharp to v112 [security] - autoclosed
Oct 12, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security] - autoclosed
chore(deps): update dependency restsharp to v112 [security]
Oct 12, 2024
marvin-serp-bot
force-pushed
the
upgrade/nuget-restsharp-vulnerability
branch
2 times, most recently
from
October 16, 2024 16:05
f4d63d2
to
a21d619
Compare
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security]
chore(deps): update dependency restsharp to v112 [security] - autoclosed
Oct 17, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security] - autoclosed
chore(deps): update dependency restsharp to v112 [security]
Oct 17, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security]
chore(deps): update dependency restsharp to v112 [security] - autoclosed
Oct 17, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security] - autoclosed
chore(deps): update dependency restsharp to v112 [security]
Oct 17, 2024
marvin-serp-bot
force-pushed
the
upgrade/nuget-restsharp-vulnerability
branch
from
October 17, 2024 14:05
a21d619
to
0d91023
Compare
marvin-serp-bot
force-pushed
the
upgrade/nuget-restsharp-vulnerability
branch
3 times, most recently
from
December 12, 2024 19:05
d17db84
to
a16c3bf
Compare
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security]
chore(deps): update dependency restsharp to v112 [security] - autoclosed
Dec 12, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security] - autoclosed
chore(deps): update dependency restsharp to v112 [security]
Dec 12, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security]
chore(deps): update dependency restsharp to v112 [security] - autoclosed
Dec 13, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security] - autoclosed
chore(deps): update dependency restsharp to v112 [security]
Dec 13, 2024
marvin-serp-bot
force-pushed
the
upgrade/nuget-restsharp-vulnerability
branch
from
December 13, 2024 14:06
a16c3bf
to
22784da
Compare
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security]
chore(deps): update dependency restsharp to v112 [security] - autoclosed
Dec 15, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security] - autoclosed
chore(deps): update dependency restsharp to v112 [security]
Dec 15, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security]
chore(deps): update dependency restsharp to v112 [security] - autoclosed
Dec 15, 2024
marvin-serp-bot
changed the title
chore(deps): update dependency restsharp to v112 [security] - autoclosed
chore(deps): update dependency restsharp to v112 [security]
Dec 16, 2024
marvin-serp-bot
force-pushed
the
upgrade/nuget-restsharp-vulnerability
branch
from
January 7, 2025 13:09
22784da
to
365934e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
110.2.0
->112.0.0
GitHub Vulnerability Alerts
CVE-2024-45302
Summary
The second argument to
RestRequest.AddHeader
(the header value) is vulnerable to CRLF injection. The same applies toRestRequest.AddOrUpdateHeader
andRestClient.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:
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):
The application intends to send a single request of the form:
But as the application is vulnerable to CRLF injection the above command will instead result in the following two requests being sent:
and
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):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
v111.4.1
Compare Source
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@111.4.0...111.4.1
v111.4.0
Compare Source
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@111.3.0...111.4.0
v111.3.0
Compare Source
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@111.2.0...111.3.0
v111.2.0
Compare Source
What's Changed
Execute(request)
without methodFull Changelog: restsharp/RestSharp@111.1.0...111.2.0
v111.1.0
Compare Source
v111.0.0
Compare Source
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@110.2.0...111.0.0
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.