diff --git a/submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/.gitkeep b/submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/.gitkeep deleted file mode 100644 index e69de29b..00000000 diff --git a/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/.gitkeep b/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/.gitkeep deleted file mode 100644 index e69de29b..00000000 diff --git a/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/guidance.md b/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/guidance.md deleted file mode 100644 index 810807ca..00000000 --- a/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/guidance.md +++ /dev/null @@ -1,7 +0,0 @@ -# Guidance - -Provide a step-by-step walkthrough with a screenshot on how you exploited the vulnerability. This will speed triage time and result in faster rewards. - -Subdomain takeovers require some form of evidence that can be viewed by the team who triage this vulnerability, once you have taken over the subdomain, hosting a file containing your Bugcrowd username or the submission ID will be sufficient. Place this username or submission ID inside of a HTML comment. - -Describe the impact of the takeover from this subdomain to the company, what effect would this have towards their operations, their public image, how frequently is this domain used, is this meant to be public facing? diff --git a/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/recommendations.md b/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/recommendations.md deleted file mode 100644 index cf39746a..00000000 --- a/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/recommendations.md +++ /dev/null @@ -1,12 +0,0 @@ -# Recommendation(s) - -There is no single technique to stop subdomain takeover from occurring. However, implementing the right combination of defensive measures will prevent and limit the impact of subdomain takeover. Some best practices include the following: - -- Ensure that the business has an inventory of all domains and hosting providers and that this inventory is maintained and updated regularly to prevent dangling records. -- Clearly defined and implemented standard processes for the provisioning and deprovisioning of hosts. For example, ensure that all steps are performed closely together. When provisioning, claim the virtual host first, and create the DNS records last. When deprovisioning, remove the DNS records first. - -For more information, please see the following guides: - -- -- -- diff --git a/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/template.md b/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/template.md deleted file mode 100644 index a727b4d7..00000000 --- a/submissions/description/server_security_misconfiguration/misconfigured_dns/high_impact_subdomain_takeover/template.md +++ /dev/null @@ -1,18 +0,0 @@ -A subdomain takeover is when a misconfigured Domain Name System (DNS) record is re-registered to an endpoint owned by an attacker. An attacker is then able to redirect users to the endpoint and capture data such as cookies and credentials, perform Cross-Site Scripting (XSS) attacks, and potentially take over accounts in the legitimate application. - -A high-impact subdomain takeover vulnerability was identified which could impact the reputation and brand of the business. An attacker can register a subdomain on behalf of the target domain and use it to create a HTML document with JavaScript payload that triggers a Cross-Site Scripting (XSS) attack. The target domain can also be used to create a scenario where an attacker can harvest user credentials by phishing users who then visit and login on a cloned version of a legitimate website. - -**Business Impact** - -High-Impact subdomain takeover could lead to data theft and indirect financial loss through the attacker’s ability to interact with legitimate users. These malicious actions could also result in reputational damage for the business through the impact to customers’ trust. - -**Steps to Reproduce** - -1. Browse to the URL `takeover.inscope.com/proof.txt` -1. You will see a Bugcrowd Username which matches the HTML comment in the Proof of Concept - -**Proof of Concept (PoC)** - -The following screenshot show the success of a subdomain takeover: - -{{screenshot}} diff --git a/submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/guidance.md b/submissions/description/server_security_misconfiguration/misconfigured_dns/subdomain_takeover/guidance.md similarity index 100% rename from submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/guidance.md rename to submissions/description/server_security_misconfiguration/misconfigured_dns/subdomain_takeover/guidance.md diff --git a/submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/recommendations.md b/submissions/description/server_security_misconfiguration/misconfigured_dns/subdomain_takeover/recommendations.md similarity index 100% rename from submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/recommendations.md rename to submissions/description/server_security_misconfiguration/misconfigured_dns/subdomain_takeover/recommendations.md diff --git a/submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/template.md b/submissions/description/server_security_misconfiguration/misconfigured_dns/subdomain_takeover/template.md similarity index 55% rename from submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/template.md rename to submissions/description/server_security_misconfiguration/misconfigured_dns/subdomain_takeover/template.md index bca830d6..d6771c72 100644 --- a/submissions/description/server_security_misconfiguration/misconfigured_dns/basic_subdomain_takeover/template.md +++ b/submissions/description/server_security_misconfiguration/misconfigured_dns/subdomain_takeover/template.md @@ -1,10 +1,10 @@ A subdomain takeover is when a misconfigured Domain Name System (DNS) record is re-registered to an endpoint owned by an attacker. An attacker is then able to redirect users to the endpoint and capture data such as cookies and credentials, perform Cross-Site Scripting (XSS) attacks, and potentially take over accounts in the legitimate application. -A basic subdomain takeover vulnerability was identified which could impact the reputation and brand of the business. An attacker can register a subdomain on behalf of the target domain and use it for spamming and phishing attacks. +A subdomain takeover vulnerability was identified which could impact the reputation and brand of the business. An attacker can register a subdomain on behalf of the target domain and use it for spamming and phishing attacks. **Business Impact** -Basic subdomain takeover could lead to data theft and indirect financial loss through the attacker’s ability to interact with legitimate users. These malicious actions could also result in reputational damage for the business through the impact to customers’ trust. +Subdomain takeover can lead to data theft and indirect financial loss through the attacker’s ability to interact with legitimate users. These malicious actions could also result in reputational damage for the business through the impact to customers’ trust. **Steps to Reproduce** @@ -14,5 +14,5 @@ Basic subdomain takeover could lead to data theft and indirect financial loss th **Proof of Concept (PoC)** The following screenshot show the success of a subdomain takeover: - -{{screenshot}} +> +> {{screenshot}}