Skip to content

Security Report: Subdomain Takeover of ipfs.guild.xyz Pointing to Pinata #36

@aparcekarl

Description

@aparcekarl

Description
Title: Web3 Application Security Testing

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

Priority= P2 (HIGH)

Description

Hi Guild Team,

Recently, I just found some of your subdomains (*guild.xyz) pointing to the vulnerable Third Party site "Pinata" This issue is about your subdomain being misconfigured in Pinata.

https://ipfs.guild.xyz

Image

I discovered that this subdomain guild.xyz has an error with Pinata meaning a non-connection with any project. Based on my past discoveries, this is a possible subdomain takeover.

I temporarily took the subdomain and hosted a sample directory. Please take a look

https://ipfs.guild.xyz/ipfs/QmaBwrziFQnmKxnKVeyaUmpd3i2DbjR3NE1eT3ZuMtB36e

Image

Impact:

Based on the vulnerability. The impact here is that the attacker can have full access to the subdomain's content. Which can create a full copy of the Web Application Used by Guild.xyz
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 *guild.xyz 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 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions