Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 328,242 coordinated disclosures
190,096 fixed vulnerabilities
401 bug bounties with 855 websites
9,185 researchers, 852 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-411221

Security Researcher qiece Helped patch 206 vulnerabilities
Received 3 Coordinated Disclosure badges
Received 5 recommendations
, a holder of 3 badges for responsible and coordinated disclosure, found a security vulnerability affecting bafangpublic.oss-cn-hangzhou.aliyuncs.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:bafangpublic.oss-cn-hangzhou.aliyuncs.com  
Open Bug Bounty Program:Create your bounty program now. It's open and free.
Vulnerable Application:Custom Code
Vulnerability Type:XSS (Cross Site Scripting) / CWE-79
CVSSv3 Score:6.1 [CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N]
Discovered and Reported by:qiece Helped patch 206 vulnerabilities
Received 3 Coordinated Disclosure badges
Received 5 recommendations
Remediation Guide:OWASP XSS Prevention Cheat Sheet

Vulnerable URL:

Screenshot: bafangpublic.oss-cn-hangzhou.aliyuncs.com  vulnerability

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:12 November, 2017 14:29 GMT
Vulnerability Verified:12 November, 2017 14:31 GMT
Website Operator Notified:12 November, 2017 14: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]:
12 November, 2017 14: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.10 February, 2018 14:29 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.

bafangpublic.oss-cn-hangzhou.aliyuncs.com

Website Overview

Alexa Global Rank:N/A
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
unpatched
12.11.2017

  Latest Patched

 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
 19.03.2019 motionelements.com
 19.03.2019 klarmobil.de
 19.03.2019 etsu.edu
 19.03.2019 cutt.us
 19.03.2019 xe.gr

  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

    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
     DevTkd:
Thank you for your expressive vulnerability report. You do a great job. Thank you very much.
    15 March, 2019
     fkmclane:
Thanks for finding and responsibly reporting vulnerabilities in our websites and making them more secure!