-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CRLF in dio.request #1130
Comments
I have tested |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still an issue, please make sure it is up to date and if so, add a comment that this is still an issue to keep it open. Thank you for your contributions. |
Hi, thanks in advance! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still an issue, please make sure it is up to date and if so, add a comment that this is still an issue to keep it open. Thank you for your contributions. |
Hi guys, Your bot just closed CVE related issue without fix. This CVE was scored as high(https://nvd.nist.gov/vuln/detail/CVE-2021-31402). |
Maybe we should let the repo's owner reopen this issue. |
As a record, this issue has been resolved by 927f79e already according to dart-lang/sdk@6abb6e5. The issue should not occur from 5.0 versions and above. |
New Issue Checklist
Issue Info
ENV: Any
Examples generated on:
Issue Description and Steps
Please consider given snippet:
Generated call looks like
Which presents a security issue. Classic CRLF injection.
Vector attack:
If the attacker controls the HTTP method(verb), he can change a call and steal all cookies, session whatever is in a call.
Assuming flow like
USER
->FOO
->BAR
, where flow betweenFOO
andBAR
is internal, mentioned data may leak.Let's assume I'm replacing example.com with my-hackery-uservice.org and the victim(service) is working in a company behind the proxy. This means I can easily redirect calls with headers/cookies(tokens) and blah blah blah. By doing more advanced CRLF I can remove the requirement for proxy at all.
Expected behavior:
if HTTP method(verb) is invalid, raise error.
The text was updated successfully, but these errors were encountered: