Does "Sorry, this store is currently unavailable" mention to shopify subdomain takeover? about can-i-take-over-xyz HOT 7 OPEN

stop spamming!!

Not a spam! I'm deeply invested in resolving this issue as it's crucial for my bug hunting efforts.

from can-i-take-over-xyz.

stop spamming!!

Not a spam! I'm deeply invested in resolving this issue as it's crucial for my bug hunting efforts.

You re right. Now that you say it, it's not spam.

Thank you for understanding. Let me know if you have any insights or suggestions regarding the issue at hand

from can-i-take-over-xyz.

.

from can-i-take-over-xyz.

"Upon visiting the domain, I received the message "Sorry, this store is currently unavailable." However, Shopify indicates that the same domain, flagged as vulnerable to takeover by Nuclei, is currently in use. Can someone clarify this discrepancy and its implications for subdomain takeover?

Usually only those shopify domains which have myshopify.com or shops.myshopify.com in their cname are vulnerable to subdomain takeovers only if they are not connected with another shopify store account.
Coming to your question , i can't exactly tell whats main reason but i can guess its maybe the shop is not in "Publish" mode but is connected with another shopify account or maybe that shopify account trail period is expired while that domain is still connected to this shopify account.

Same behaviours can be observed in other hosting services too , such as amazon and azure (s3 buckets, elastibeanstalk domains, trafficmanager domains , etc ) - In normal sight some of these subs connected to these services may seem unclaimed and dead but they are somehow shown as "Already in use" in these services hosting panels.

from can-i-take-over-xyz.

"Upon visiting the domain, I received the message "Sorry, this store is currently unavailable." However, Shopify indicates that the same domain, flagged as vulnerable to takeover by Nuclei, is currently in use. Can someone clarify this discrepancy and its implications for subdomain takeover?

Usually only those shopify domains which have myshopify.com or shops.myshopify.com in their cname are vulnerable to subdomain takeovers only if they are not connected with another shopify store account. Coming to your question , i can't exactly tell whats main reason but i can guess its maybe the shop is not in "Publish" mode but is connected with another shopify account or maybe that shopify account trail period is expired while that domain is still connected to this shopify account.

Same behaviours can be observed in other hosting services too , such as amazon and azure (s3 buckets, elastibeanstalk domains, trafficmanager domains , etc ) - In normal sight some of these subs connected to these services may seem unclaimed and dead but they are somehow shown as "Already in use" in these services hosting panels.

Thanks for your clarification. I was wondering how nuclei template flags this as a matcher while it is not accurate 100%

from can-i-take-over-xyz.

.

from can-i-take-over-xyz.

"Upon visiting the domain, I received the message "Sorry, this store is currently unavailable." However, Shopify indicates that the same domain, flagged as vulnerable to takeover by Nuclei, is currently in use. Can someone clarify this discrepancy and its implications for subdomain takeover?

Usually only those shopify domains which have myshopify.com or shops.myshopify.com in their cname are vulnerable to subdomain takeovers only if they are not connected with another shopify store account. Coming to your question , i can't exactly tell whats main reason but i can guess its maybe the shop is not in "Publish" mode but is connected with another shopify account or maybe that shopify account trail period is expired while that domain is still connected to this shopify account.
Same behaviours can be observed in other hosting services too , such as amazon and azure (s3 buckets, elastibeanstalk domains, trafficmanager domains , etc ) - In normal sight some of these subs connected to these services may seem unclaimed and dead but they are somehow shown as "Already in use" in these services hosting panels.

Thanks for your clarification. I was wondering how nuclei template flags this as a matcher while it is not accurate 100%

i guess this is the template for shopify sub takeovers you used : https://github.com/projectdiscovery/nuclei-templates/blob/4aef6c0933ecab9242853a4146a01c69e531e03b/http/takeovers/shopify-takeover.yaml

The template purpose is to grep for those certain words or "fingerprints" and if matches are found , then its shown in nuclei output result. The template is working well for its intended purpose. However, we can't solely rely on fingerprints to verify if any sub is indeed vulnerable to subdomain takeover , we need to verify it manually in their respective hosting service.

And always remember, the nuclei tool and its templates are written by humans , the templates can have incorrections sometimes , so dont trust them blindly , always verify their results manually before reporting them to bugbounty programs.

Hope you got your answer.

from can-i-take-over-xyz.