search

better-internet / radworks-docs

15 stars 28 forks source link

Security Report: Domain Takeover of http://docs.radicle.xyz/Pointing to Netlify #242

Closed aparcekarl closed 1 year ago

aparcekarl commented 1 year ago

Title: Web Application Security Testing

Bug type = Server Security Misconfiguration > Misconfigure DNS > High Impact Subdomain Takeover

Priority= P2 (HIGH)

Description

Hi Radicle Team,

Recently, i just found some of your domain (*radicle.xyz) pointing to vulnerable Third Party site "Netlify" This issue is about your main domain being misconfigured in Netlify

http://docs.radicle.xyz/

POC1

Reconnaissance

I began with enumerating subdomains using turbolist3r when i stumbled upon interesting subdomain “docs.radicle.xyz”.

I used a command in CMD python (http://turbolist3r.py/) -v -b -d radicle.xyz -a

I Verified the Cname record via MX Toolbox for DNS record check

I discovered that this subdomain “docs.radicle.xyz” is having an error with Netlify meaning a non-connection with any project. Base in my past discoveries, this is a possible subdomain takeover

Steps to Reproduce

  1. Go to Netlify and create an account
  2. Create a new project and deploy a sample app
  3. Go to Settings>Domains
  4. Then add the vulnerable subdomain docs.radicle.xyz
  5. Ownership is done.

Risk Breakdown

Risk: Severe Difficulty to Exploit: Easy Complexity: Easy Weakness Categories: Deployment Misconfiguration/Stored XSS/Authentication Bypass (CWE: 16) CVSS2 Score: 9.3 (AV:N/AC:M/Au:S/C:C/I:C/A:N)

Reference: https://0xpatrik.com/subdomain-takeover/

Remediations

  1. Check your DNS-configuration for subdomains pointing to services, not in use
  2. Set up your external service so it fully listens to your wildcard DNS.
  3. Our advice is to keep your DNS entries constantly vetted and restricted.
  4. Preventing subdomain takeovers is a matter of order of operations in lifecycle management for virtual hosts and DNS. Depending on the size of the organization, this may require communication and coordination across multiple departments, which can only increase the likelihood for a vulnerable misconfiguration.
  5. Create an inventory of all of your organization’s domains and their hosting providers, and update it as things change, to ensure that nothing is left dangling

Thank you

aparcekarl commented 1 year ago

Hi there,

Do you have updates? Thank you

shelbeeee commented 1 year ago

Hey there @aparcekarl - the docs.radicle.xyz has been sunsetted for now as they work on a new version of docs for radicle.xyz.

aparcekarl commented 1 year ago

This should not be left open that will lead to a vulnerability like this

adaszko commented 1 year ago

Hi and thanks for reporting! I went through all the subdomains and deleted obsolete/dead ones to avoid any potential security breaches.

aparcekarl commented 1 year ago

Thank you. This is all fixed now. Great work I hope this will be eligible for a bug bounty