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

Statuspage no longer vulnerable #65

Merged
merged 2 commits into from
Nov 18, 2018
Merged

Conversation

Kushagra
Copy link
Contributor

@Kushagra Kushagra commented Nov 9, 2018

Statuspage no longer vulnerable to subdomain takeover because they ask users to put this [unique_string].stspg-customer.com in CNAME instead of just statuspage.io

https://help.statuspage.io/knowledge_base/topics/domain-ownership - Custom Domain

Statuspage no longer vulnerable to subdomain takeover because they ask users to put this `[unique_string].stspg-customer.com` in CNAME instead of just `statuspage.io`

https://help.statuspage.io/knowledge_base/topics/domain-ownership - Custom Domain
@codingo
Copy link
Collaborator

codingo commented Nov 10, 2018

What's the length of the unique string? This way of correcting this is often brute forcible (Amazon ELB's, for example).

Do you have a sample DNS record?

@Kushagra
Copy link
Contributor Author

Kushagra commented Nov 10, 2018

  1. tqft9l15ml0m.stspg-customer.com

@EdOverflow
Copy link
Owner

Thank you for the pull request, @Kushagra. Would it be possible to add a reference in the table to this ticket for context?

@Kushagra
Copy link
Contributor Author

Added. @EdOverflow

@EdOverflow EdOverflow merged commit 62f4c5f into EdOverflow:master Nov 18, 2018
@EdOverflow
Copy link
Owner

Thank you, @Kushagra.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants