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

AWS Route 53 #1

Open
ghost opened this issue May 31, 2021 · 5 comments
Open

AWS Route 53 #1

ghost opened this issue May 31, 2021 · 5 comments
Labels
Not Vulnerable This service is not vulnerable to takeover.

Comments

@ghost
Copy link

ghost commented May 31, 2021

Service AWS Route 53

Status Not Vulnerable

Nameservers

ns-****.awsdns-**.org
ns-****.awsdns-**.co.uk
ns-***.awsdns-**.com
ns-***.awsdns-**.net

Explanation

AWS Route 53 is no longer vulnerable to DNS takeovers even when SERVFAIL errors are returned due to changes by the team that stops takeovers via newly created zones. This has been independently verified.

@ghost ghost added the Not Vulnerable This service is not vulnerable to takeover. label May 31, 2021
@ghost ghost closed this as completed May 31, 2021
@indianajson indianajson reopened this Jun 1, 2021
@indianajson indianajson changed the title AWS Route 53 - No Longer Vulnerable AWS Route 53 Jun 12, 2021
@0xpr4bin
Copy link

But can't we match the nameservers on hit and trial basis,deleting and creating zone until one of the ns matches

@indianajson
Copy link
Owner

@0xpr4bin This was patched for the most part where AWS won't serve the previously assigned NS pairs. It can happen in a very limited number of scenarios but as far as we are aware this is effectively patched.

@schniggie
Copy link

Have received a couple of successful NS takeovers over the last week. So I would recommend setting the label back to vulnerable.

@ertygiq
Copy link

ertygiq commented Dec 18, 2023

@schniggie can you describe what steps you took?

@viszsec
Copy link

viszsec commented Jan 18, 2024

Have received a couple of successful NS takeovers over the last week. So I would recommend setting the label back to vulnerable.

Could you please show us proof of your claims? Stating baseless claims without facts or proof is merely a fallacy.

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

No branches or pull requests

5 participants