Security Report: Subdomain Takeover of https://pay.mstable.io// Pointing to Godaddy

[transferwisea]

Title: Web Application Security Testing

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

Priority= P2 (HIGH)

Description

Hi Mstable Team,

Recently, i just found some of your subdomain (*mstable.io) pointing to vulnerable Third Party site "Godaddy" This issue is about your subdomain being misconfigured in Godaddy

https://pay.mstable.io/

Reconnaissance

I began with enumerating subdomains using turbolist3r when i stumbled upon interesting subdomain “mstable.io”.

I Verified the Cname record via MX Toolbox for DNS record check I discovered that this subdomains are having an error with Godaddy meaning a non-connection with any project. Base in my past discoveries, this is a possible subdomain takeover

Proof of Concept

Steps to Reproduce

1. Go to your GoDaddy Dashboard
2. Setup GoDaddy Payments
3. Go to Payment Hub> Set up Payouts
4. Publish your site to enable the checkout portal
5. Ownership is done.

Impact:

Based on the vulnerability. The impact here is the attacker can have the full access to the subdomain's content. Which can create a full copy of the Web Application Used by mstable.io

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 legitimate *mstable.io 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)

Remediation

• 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