oxidecomputer / oxidecomputer/dropshot
Test that requests with large request Content-Length cannot cause a denial-of-service
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 104
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
Description
HTTP does not specify a limit on request body size but allows implementations to enforce one to allow bounding of resource usage. Even if the actual request body is small, direct usage of a client-supplied Content-Length header can cause excessive memory usage potentially leading to a denial-of-service. Dropshot has a config option to set a maximum request body size but no test to verify that that limit is enforced for this case.
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
Locate the Dropshot configuration for the maximum request body size and the existing request-size tests or request handling entry points. Add a test using a large client-supplied Content-Length with a small body, then run the relevant Rust tests to verify the configured limit is enforced without excessive resource use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100