-
-
Notifications
You must be signed in to change notification settings - Fork 741
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
surge.sh is not vulnerable #198
Comments
Hey!! I just got the same scenario and this is still a takeover, you have to add a CNAME file in the same directory. |
@yashanand Can you please explain step by step? Like what all you did to takeover the subdomain. |
Hey I follow the same steps which are given on the official website, if you have any doubt ping me on Twitter @yashanand155 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am bit confused about
how takeovers works
so If a website named
sub.target.com
is pointing towardthisisrandom.surge.sh
then the way to takeover would be to register thethisisrandom.surge.sh
domain, right?If that is how it should be then it's not possible to takeover
surge.sh
subdomains. I don't think it's possible because when you go on to register a new project with a new subdomain it checks if that subdomain is registered by someone else or not. And if it then it give errorPlease let me know if I'm wrong and someone finds a way to take these over :)
The text was updated successfully, but these errors were encountered: