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

Subdomain takevoer at v.eslint.cn #18

Open
klau5dev opened this issue Sep 1, 2020 · 0 comments
Open

Subdomain takevoer at v.eslint.cn #18

klau5dev opened this issue Sep 1, 2020 · 0 comments

Comments

@klau5dev
Copy link

klau5dev commented Sep 1, 2020

Hi. I'm a bug bounty hunter. While I check eslint bug, I just found that "v.eslint.cn" domain is vaulnerable for subdomain takeover attack. I thought this domain's owner is eslint and report this bug, but they said it's not their domain. So I report here.

Subdomain takeover vulnerabilities occur when a subdomain (subdomain.example.com) is pointing to a service (e.g. GitHub pages, Heroku, etc.) that has been removed or deleted. This allows an attacker to set up a page on the service that was being used and point their page to that subdomain. For example, if subdomain.example.com was pointing to a GitHub page and the user decided to delete their GitHub page, an attacker can now create a GitHub page, add a CNAME file containing subdomain.example.com, and claim subdomain.example.com. (refer from https://github.com/EdOverflow/can-i-take-over-xyz)

I tried tracing and I think the reason of this bug is Fastly configuration.

Visit http://v.eslint.cn then you can check my PoC page. If you want to remove this vulnerability, change Fastyly configuration. This issue can be exploited in several ways, for example but not limited to: XSS, Phishing.

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

No branches or pull requests

1 participant