mandatoryprogrammer / mandatoryprogrammer/CursedChrome
Streaming HTTP responses not handled
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
The current setup requires the HTTP response to completely finish to be able to return the response to the headers. In some situations, a website will reply with a response of unknown length and use it to stream data as response to other events. This will not work and the request will instead just timeout on the attacker side.
PS. Sorry for dropping a batch of issues like this. We have an ambition of providing PRs as well but letting you know about these things straight away in the meantime.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by tracing the HTTP response-handling path and reproduce a response with unknown length that streams data; done means the response can be returned to the headers without waiting for completion or timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100