-
Notifications
You must be signed in to change notification settings - Fork 375
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
Add tiny-http Request Smuggling #355
Merged
Shnatsel
merged 2 commits into
rustsec:master
from
snoopysecurity:add-tiny-http-request-smuggling
Aug 21, 2020
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
[advisory] | ||
id = "RUSTSEC-2020-0000" | ||
package = "tiny_http" | ||
date = "2020-06-16" | ||
title = "HTTP Request smuggling through malformed Transfer Encoding headers" | ||
url = "https://github.com/tiny-http/tiny-http/issues/173" | ||
categories = ["format-injection"] | ||
keywords = ["http", "request-smuggling"] | ||
description = """ | ||
HTTP pipelining issues and request smuggling attacks are possible due to incorrect | ||
Transfer encoding header parsing. | ||
|
||
It is possible conduct HTTP request smuggling attacks (CL:TE/TE:TE) by sending invalid Transfer Encoding headers. | ||
|
||
By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information | ||
from requests other than their own. | ||
""" | ||
|
||
[versions] | ||
patched = [] |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think "format injection" is quite correct; we do not seem to have a proper category for this.
I suppose we should eventually transition to CWE, but in the meanwhile it's probably best to just drop the category field here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah agreed, this is an injection vulnerability, but the
format-injection
category is more precisely intended for "format string injection" vulnerabilities.Also agreed it'd be nice to implement CWE.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, CWE would be nice