opensafely-core / opensafely-core/reports
There is a risk of a DoS attack by repeatedly busting the cache and then hitting Github API rate limiting
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
See discussion here: https://ebmdatalab.slack.com/archives/C02143357LM/p1623059622273000
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
Start with the linked Slack discussion to understand the cache-busting and GitHub API rate-limit scenario, then locate the report site's cache and GitHub API integration. Done means preventing repeated cache busting from exhausting the API rate limit, with the expected behavior agreed from the discussion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100