Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Digital Ocean #22

Open
indianajson opened this issue Jun 11, 2021 · 7 comments
Open

Digital Ocean #22

indianajson opened this issue Jun 11, 2021 · 7 comments
Labels
Vulnerable This service is vulnerable to takeover.

Comments

@indianajson
Copy link
Owner

indianajson commented Jun 11, 2021

Service Digital Ocean

Status Vulnerable

Nameserver

ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

Explanation

To perform a takeover create a new account on Digital Ocean and follow the DNS quick start guide. In short, once inside the Dashboard click on the big green Create button and select Domains/DNS. Enter the vulnerable domain in the form field labeled Enter domain. If the page allows you to create the zone the takeover was successful.

Digital Ocean's vulnerability to DNS takeovers was discussed in detail by Matthew Bryant in 2016 and they are still vulnerable today.

@indianajson indianajson added the Vulnerable This service is vulnerable to takeover. label Jun 11, 2021
@indianajson indianajson changed the title Digital Ocean - Vulnerable Digital Ocean Jun 12, 2021
@FalcoXYZ
Copy link

For anyone wondering, this is still vulnerable in 2023.

@dend
Copy link

dend commented Mar 19, 2024

And in 2024, Digital Ocean is still vulnerable.

@fa1c0n1
Copy link

fa1c0n1 commented Jun 2, 2024

But now, I found Digital Ocean uses Cloudflare as their NS:
kim.ns.cloudflare.com.
walt.ns.cloudflare.com.

So, does it mean Digital Ocean is not vulnerable anymore?

@indianajson
Copy link
Owner Author

@fa1c0n1 Possibly, yes. I'm surprised they moved to Cloudflare but I will need to test.

@thetorpedodog
Copy link

But now, I found Digital Ocean uses Cloudflare as their NS: kim.ns.cloudflare.com. walt.ns.cloudflare.com.

So, does it mean Digital Ocean is not vulnerable anymore?

While Digital Ocean uses Cloudflare to serve DNS for their own domain, the DNS services they provide are still vulnerable to takeover—everybody gets the same nameservers, and there is no verification of ownership.

@domdefault
Copy link

I'm new to this, do I need to create an app and publish a txt to prove I have taken it over? my current issue is that the domain isn't transferring to my account.

@indianajson
Copy link
Owner Author

@domdefault Yes, you'd create an account, add the domain to your account by creating a zone with that domain name (or subdomain) then adding a TXT record to the zone.

You can send them a link to Google's DNS checker as your POC like this: https://toolbox.googleapps.com/apps/dig/#TXT/myexample.com

Just be sure to check there an hour after you add the TXT record to make sure it worked before you report. Once you create the zone you're the only one who can report it with a POC so there's no hurry at that point.

Happy to help if you need. DM me on Twitter or Discord (but mention it here cause my notification on Twitter aren't working).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Vulnerable This service is vulnerable to takeover.
Projects
None yet
Development

No branches or pull requests

6 participants