Open Bug Bounty selected among the
Top 5 Bug Bounty programs to watch
in 2021 by The Hacker News

For security researchers
Report a Vulnerability
Submit, help fixing, get kudos.
For website owners
Start a Bug Bounty
Run your bounty program for free.
1,100,320 coordinated disclosures
670,305 fixed vulnerabilities
1,437 bug bounty programs, 2,861 websites
25,192 researchers, 1,375 honor badges

my-shop Bug Bounty Program

my-shop 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 my-shop

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

Bug bounty program allow private submissions only.

Bug Bounty Scope

The following websites are within the scope of the program:

*.my-shop.ru

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:

We require that all researchers follow the following testing and reporting rules:

If you are able to expose PII (personally identifying information) as a result of your testing, please stop testing and submit the vulnerability and do not include PII in your report submission. This is for compliance reasons.
Stop testing and report the issue immediately if you gain access to any non-public application or non-public credentials.
Only interact with accounts you own or with the explicit permission of the account holder.
Perform research only within the scope set out below.
To the extent that you have accessed non-public My-Shop information in the course of your research, you do not maintain copies of any such information or share any such information with any third party.
You do not publicly disclose or share the vulnerability details without the written permission of My-Shop.

Testing Requirements:

Vulnerability reports which do not include careful manual validation - for example, reports based only on results from automated tools and scanners or which describe theoretical attack vectors without proof of exploitability - will be closed as Not Applicable.

The My-Shop Bug Bounty program consider excluding vulnerability classes below:

Self-XSS
Tabnabbing
Clickjacking
Flash-based XSS
Cookie expiration
Cookie valid after logout
Issues related to rate limiting
Internal IP address disclosure
Reveal internal class information
Unauthenticated/logout/login CSRF
Cookie valid after password change/reset
Missing best practices in SSL/TLS configuration
Weak password policies & Password policies bypass
Attacks requiring MITM or physical access to a user's device
Any activity that could lead to the disruption of our service (DoS)
Previously known vulnerable libraries without a working Proof of Concept
Weak Captcha & Captcha bypass (excluded only for testing environments)
Login or Forgot Password page brute force and account lockout not enforced
Vulnerabilities only affecting users of outdated or unpatched browsers and platforms
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Username enumeration on customer-facing systems (i.e. using server responses to determine whether a given account exists)
Vulnerabilities that only affect one browser will be considered on a case-by-case basis and may be closed as informative due to the reduced attack surface
Vulnerability reports that require a large amount of user cooperation to perform, unlikely or unreasonable actions which would be more symptomatic of a social engineering or phishing attack and not an application vulnerability (e.g. disabling browser security features, sending the attacker critical information to complete the attack, guiding the user through a particular flow and requiring them to enter malicious code themselves, etc.)

Possible Awards:

Wall of fame

Special Notes:

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. Violation of these requirements may result in permanent disqualification from the program.
Any activity determined to involve the intentional compromise of the privacy of our customers or employees or the intentional disruption of the operation of our products, services or IT infrastructure will result in permanent disqualification from the program.

Feedback

If you have suggestions for improving this program, please let us know at [email protected]

Community Rating

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

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

Researcher's comments

No comments so far.

  Latest Patched

 19.10.2021 ulakbim.gov.tr
 19.10.2021 societe.com
 19.10.2021 tga.gov.au
 19.10.2021 mydomain.com
 19.10.2021 ipower.com
 19.10.2021 picuki.com
 19.10.2021 filmdaily.co
 19.10.2021 fileforum.com

  Latest Blog Posts

08.10.2021 by NNeuchi
How I Found My First Bug Reflected Xss On PIA.GOV.PH(Philippine Information Agency)
26.08.2021 by PyaePhyoThu98
eG Manager v7.1.2: Improper Access Control lead to Remote Code Execution (CVE-2020-8591)
14.07.2021 by Open Bug Bounty
Interview With Open Bug Bounty
25.05.2021 by 0xrocky
Google XSS Game
25.05.2021 by ShivanshMalik12
Testing for XSS (Cross Site Scripting)

  Recent Recommendations

@LangweileDich     20 October, 2021
    Twitter LangweileDich:
Thanks to Chiraq for informing me about data that was publicy accessible and how to fix it.
@sammy2000m     20 October, 2021
    Twitter sammy2000m:
Thanks to mistry4592
our team would like to thank you for finding vulnerability on our website.
@xnih     18 October, 2021
    Twitter xnih:
Thanks to mistry4592 for his report and extra feedback on the issue. He was quick to provide us a link to reproduce the issue when asked!
@AlexisMousset     18 October, 2021
    Twitter AlexisMousset:
Pramod has reported a potential vulnerability on our website.

Thank you!
@LangweileDich     15 October, 2021
    Twitter LangweileDich:
Thanks for letting me know of an abandoned file that needed to be deleted.