Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 328,646 coordinated disclosures
190,464 fixed vulnerabilities
407 bug bounties with 862 websites
9,206 researchers, 854 honor badges

united-domains AG Bug Bounty Program

united-domains AG runs a bug bounty program to ensure the highest security and privacy of its websites. Everyone is eligible to participate in the program subject to the below-mentioned conditions and requirements of united-domains AG

Open Bug Bounty performs triage and verification of the submissions. However, we never intervene to the further process of vulnerability remediation and disclosure between united-domains AG and researchers.

Bug bounty program allow private submissions only.

Bug Bounty Scope

The following websites are within the scope of the program:

blog.united-domains.de
united-domains.de
ud-reselling.com
domain-recht.de

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

- Cross Site Scripting (XSS)
- Open Redirect

- Cross Site Request Forgery (CSRF)
- Improper Access Control

General Requirements:

Data protection and security have always had a special meaning and are therefore also a special concern for united-domains. We have a deep desire to see the Internet remain as safe as possible for us all. That is why we take security issues very seriously.

We are interested in hearing about any potential security issues on united-domains websites, web services and products. To be eligible for a reward, note that we typically require the issue report to have some actual security impact in a realistic scenario. This does not mean you need to fully exploit issues, just provide the information you have, and we will analyze your report and draw conclusions on the impact.

In our opinion, the practice of responsible disclosure is the best way to safeguard the Internet. It allows individuals to notify companies like united-domains of any security threats before going public with the information. This gives us a fighting chance to resolve the problem before the criminally-minded become aware of it.

Responsible disclosure is the industry best practice, and we recommend it as a procedure to anyone researching security vulnerabilities.

We are happy to thank everyone who submits valid reports which help us improve the security of united-domains however, only those that meet the following eligibility requirements may receive a monetary reward:
* You must be the first reporter of a vulnerability.
* The vulnerability must be a qualifying vulnerability
* Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through openbugbounty.org
* You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
* You must avoid tests that could cause degradation or interruption of our service (refrain from using automated tools, and limit yourself about requests per second).
* You must not leak, manipulate, or destroy any user data.
* You must not be a former or current employee of united-domains or one of its contractor.
* Reports about vulnerabilities are examined by our security analysts. Our analysis is always based on worst case exploitation of the vulnerability, as is the reward we pay.
* No vulnerability disclosure, including partial is allowed for the moment.

Qualifying Vulnerabilities:
* Cross Site Scripting (XSS)
* Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
* Authentication and Authorization Flaws
* Cross Site Request Forgery (CSRF)
* Remote Code Execution (RCE)
* Code injections (HTML, JS, SQL, PHP, etc.)
* Insecure direct object references
* CORS
* Directory Traversal
* Privilege Escalation

Non-Qualifying Vulnerabilities:
* Self XSS
* Missing cookie flags
* SSL/TLS best practices
* Mixed content warnings
* DoS or DDoS attacks
* HTTP Host Header XSS
* Clickjacking/UI redressing
* Software version disclosure
* Stack traces or path disclosure
* Physical or social engineering attempts
* Recently disclosed 0-day vulnerabilities
* Presence of autocomplete attribute on web forms
* Vulnerabilities affecting outdated browsers or platforms
* Issues that require physical access to a victim’s computer/device
* Logout and other instances of low-severity Cross-Site Request Forgery
* Missing security-related HTTP headers which do not lead directly to a vulnerability
* Reports from automated web vulnerability scanners (Acunetix, Vega, etc.) that have not been validated
* Invalid or missing SPF (Sender Policy Framework) records (Incomplete or missing SPF/DKIM/DMARC)

We ask you to abide by the following guidelines:
* Unless united-domains gives you permission, do not disclose any issues to the public, or to any third party.
* Unless united-domains gives you permission, do not disclose any report submitted in relation to this program.
* If you have questions on timelines (to remediation, to bounty, etc.), please ask directly in the relevant report.

Testing Requirements:

There are some things we explicitly ask you not to do:
* When experimenting, please only attack test accounts you control. A Proof of Concept unnecessarily involving accounts of other end users or united-domains employee may be disqualified.
* Do not run automated scans without checking with us first.
* Do not test the physical security of united-domains offices, employees, equipment, etc.
* Do not test using social engineering techniques (phishing, vishing, et.c.)
* Do not perform DoS or DDoS attacks.
* In any way attack our end users, or engage in trade of stolen user credentials.

In scope:
www.united-domains.de
blog.united-domains.de
help.united-domains.de
domain-recht.de
ud-reselling.com

Out of scope:
All other companies and services acquired by united-domains are not in scope.

Possible Awards:

We reserve the right to adjust the bounty amount and to change the vulnerability level of the report accordingly, as well as not to make a payout if, in our opinion, the above criteria have not been met. These bounties are only a guideline.

* Low 50 €
* Medium 125 €
* High 250 €
* Critical 500 €

Special Notes:

If you have any further questions, please do not hesitate to contact us.

Other Submissions Handling

Website owner want to receive information about other vulnerabilities

Notifications:

Please send us an email to bug [at] united-domains [dot] de

General Requirements:

See above

Testing Requirements:

See above

Possible Awards:

See above

Community Rating

Provided by security researchers who reported security vulnerabilities via this bug bounty program:

 
Response Time  How quickly researchers get responses to their submissions.
Remediation Time  How quickly reported submissions are fixed.
Cooperation and Respect  How fairly and respectfully researchers are being treated.

  Latest Patched

 23.03.2019 discogs.com
 22.03.2019 jrailpass.com
 22.03.2019 esa.int
 22.03.2019 thepetitionsite.com
 22.03.2019 temp-mail.org
 22.03.2019 weloveshopping.com
 22.03.2019 sixt.de
 22.03.2019 ioffer.com
 22.03.2019 livestream.com

  Latest Blog Posts

22.03.2019 by HackerGautam
TLS 1.3 Genesis, Mechanism and Working
19.03.2019 by Open Bug Bounty
GDPR PII exposure can now be securely reported via Open Bug Bounty
24.02.2019 by ismailtsdln
Apple XSS Vulnerability - Proof of Concept (PoC)
24.02.2019 by ismailtsdln
How do you use an xss as a keylogger ?
23.02.2019 by ismailtsdln
Everything about XSS is in this source!

  Recent Recommendations

    22 March, 2019
     jcfmachado:
Thank you for your time and notification.
    19 March, 2019
     rogerdc01:
Ezio has helped me with a vulnerability. Answered very fast after some questions and showed the way to examine the issue. Very professional!
    19 March, 2019
     interactmultim1:
Thank you k0t for reporting this bug. We appreciate your work!
    19 March, 2019
     CoreInstance:
Armin, vielen Dank für deine professionelle Unterstützung! Dank deiner Hilfe, konnten wir die Schwachstelle bei unserem Kunden direkt beheben.
    18 March, 2019
     ArnY:
Un grand merci pour votre aide. Suite à votre retour rapide et précis la faille a été corrigée rapidement par nos équipes.