LIT-Protocol
Security Report: Subdomain Takeover of https://trade-manager-frontend.litprotocol.com/ Pointing to Railway App
Is there an existing issue for this?
- [x] I have searched the existing issues
SDK version
N/A
Lit Network
N/A
Description of the bug/issue
Bug type = Server Security Misconfiguration > Misconfigured DNS > High Impact Subdomain Takeover
Priority= P2 (HIGH)
Description
Hi litprotocol Team,
Recently, i just found some of your domain (*litprotocol.com) pointing to the vulnerable Third Party site "Railway". This issue is about your main domain being misconfigured.
https://trade-manager-frontend.litprotocol.com/
Reconnaissance
I Verified the Cname record via MX Toolbox for DNS record check
I discovered that this subdomain has an error with Railway, meaning a non-connection with any project. Based on my past discoveries, this is a possible subdomain takeover
Proof of Concept
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 litprotocol.com
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 *litprotocol.com 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.
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 of 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
Severity of the bug
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)
Steps To Reproduce
Go to Railway and Login your account Create a new project and deploy a sample app Go to Settings>Domains Then add the vulnerable subdomain trade-manager-frontend.litprotocol.com Ownership is done.
Link to code
trade-manager-frontend.litprotocol.com
