Bug type = Server Security Misconfiguration > Misconfigured DNS > High Impact Subdomain Takeover Priority= P2 (HIGH) Description Hi Reserve Team, Recently, i just found some of your domain (* reserve.org ) pointing to vulnerable Third Party site "Netlify". This issue is about your main domain being misconfigured on Netlify. Host: http://www.developer.reserve.org/ Cname: protocol-tech-website.netlify.app Reconnaissance I Verified the Cname record via MX Toolbox for DNS record check I discovered that this subdomain has an error with Netlify, meaning a non-connection with any project. Based in my past discoveries, this is a possible subdomain takeover Proof of Concept Steps to Reproduce * Go to Netlify and Login your account * Create a new project and deploy a sample app * Go to Settings>Domains * Then add the vulnerable subdomain www.developer.reserve.org * Ownership is done. I temporarily takeover the Cname record for PoC purposes. Impact: Based on the vulnerability. The impact here is that the attacker can have full access to the subdomain's content. One Example: Initiating Malicious Transactions The impact of this is that the transactions are being requested from a reputable project, so people would not hesitate to sign the transaction since the subdomain is from reserve.org . The process is to connect to the blockchain via Web3 and a crypto wallet such as MetaMask on the victim’s browser to process the transaction to an attacker-owned address. 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) Remediations * Check your DNS-configuration for subdomains pointing to services, not in use * Set up your external service so it fully listens to your wildcard DNS. * Our advice is to keep your DNS entries constantly vetted and restricted. * 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. * 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
