Question: Why hasn't this been fixed?

Open
#4 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

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.

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.

Dominant language
Python
Stars
526
Forks
134
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mandatoryprogrammer/cloudflare_enum

All issues in mandatoryprogrammer/cloudflare_enum

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.