mandatoryprogrammer / mandatoryprogrammer/cloudflare_enum
Question: Why hasn't this been fixed?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 526
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
Can't CloudFlare fix this? I'm assuming it's been reported to them, right? It seems like a major security flaw as it allows people to bypass their entire system if they can figure out the A record.
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
The issue names no files, tests, or entry points. Start by reviewing the Cloudflare DNS enumeration behavior described in the report and the project's current scope; determine whether a specific, reproducible security defect and an actionable change can be defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100