Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 328,405 coordinated disclosures
190,166 fixed vulnerabilities
405 bug bounties with 859 websites
9,193 researchers, 853 honor badges

Are you sure you want to delete the vulnerability?

Yes No

This feature enables you to send additional notifications to the website owners or admins after the vulnerability is submitted. The total number of additional notification is limited to 10, and to 1 in 24 hours.

Notify specific security contact:


To my best knowledge this email belongs to the website owner/admin


Open Bug Bounty ID: OBB-49284

Security Researcher Dshellnoi_Unix, found a security vulnerability affecting duckduckgo.com website and its users.

Following coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has:

      a. verified the vulnerability and confirmed its existence;
      b. notified the website operator about its existence.

Affected Website:duckduckgo.com  
Open Bug Bounty Program:Create your bounty program now. It's open and free.
Vulnerable Application:Custom Code
Vulnerability Type:Open Redirect / CWE-601
CVSSv3 Score:3.4 [CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:N]
Discovered and Reported by:Dshellnoi_Unix
Remediation Guide:OWASP Open Redirect Cheat Sheet

Vulnerable URL:

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:17 September, 2014 04:11 GMT
Vulnerability Verified:18 September, 2014 10:31 GMT
Website Operator Notified:18 September, 2014 10:31 GMT
a. Using publicly available security contacts
b. Using Open Bug Bounty notification framework
c. Using security contacts provided by the researcher
Public Report Published
[without any technical details]:
18 September, 2014 10:31 GMT
Public Disclosure:  A security researcher can delete the report before public disclosure, afterwards the report cannot be deleted or modified anymore. The researcher can also postpone public disclosure date as long as reasonably required to remediate the vulnerability.17 September, 2014 04:11 GMT

For Website Operators and Owners

Please contact the researcher directly to get the vulnerability details. The researcher may also help you fix the vulnerability and advice on how to prevent similar issues:



For remediation best practices, please also refer to OWASP remediation guidelines. More information about coordinate and responsible disclosure on Open Bug Bounty is available here.

DISCLAIMER: As a non-profit project, Open Bug Bounty never acts as an intermediary between website owners and security researchers. Our role is strictly limited to independent verification of the reports and proper notification of website owners by all available means.

duckduckgo.com

Website Overview

Alexa Global Rank:824
SSL/TLS Server Test:N/A    
Web Server Security Test:N/A    
Malware Test:Click here
Domain Health Report:Click here

Latest Submissions

OBB-ID Reported by Status Reported on
patched
12.01.2018
patched
22.11.2017
unpatched
21.11.2017
patched
21.03.2017
patched
14.07.2016
patched
23.07.2015
patched
23.07.2015
patched
22.07.2015
patched
22.07.2015
unpatched
17.09.2014

  Latest Patched

 22.03.2019 livestream.com
 21.03.2019 vuetifyjs.com
 21.03.2019 365psd.com
 21.03.2019 ecartelera.com
 21.03.2019 bergfex.at
 20.03.2019 billabong.com
 20.03.2019 gcu.ac.uk
 20.03.2019 condos.ca
 20.03.2019 yesmovies.gg
 20.03.2019 gold.de

  Latest Blog Posts

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!
20.02.2019 by drok3r
ModSecurity - ByPass XSS

  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.