Globbing Bug Bounty Program

• am.bounty.am

• Any domain or services other than listed in the list above is out of the scope.
• iOS and Android applications

• When you are creating a Globbing account for test purposes, please add the “bugbounty_” prefix to the username of your test account.
• Ensure that you test vulnerabilities only on accounts that you own or have permission to test on.
• Never use any findings to compromise the system, exfiltrate data or pivot to other systems. Submit your report as soon as you have discovered a vulnerability. We will pay you based on the maximum impact of your finding.
• If you stumble upon sensitive information, such as personal information, credentials, etc., during the assessment; do not save, copy, store, transfer, disclose, or otherwise retain the data or personal information.
• Do not perform social engineering, phishing, and physical security attacks against Globbing offices, users, or employees.
• It is strictly prohibited to disclose any vulnerabilities without Globbing’s explicit permission.
• Stay within the program’s scope.
• The usage of automated scanners is not allowed.
• Be respectful when you are interacting with our team.

• Sensitive Data Exposure
• Remote Code Execution (RCE)
• Server-Side Request Forgery (SSRF)
• Cross-site Scripting (XSS)
• Cross-site Request Forgery (CSRF)
• SQL Injection
• XML External Entity Attacks (XXE)
• Access Control Vulnerabilities (Insecure Direct Object Reference, Privilege Escalation, Broken Access, etc.)
• Path/Directory Traversal Issues

• Tab-nabbing.
• Click-jacking/UI-redressing, or issues only exploitable via click-jacking.
• Open redirect - unless an additional security impact can be demonstrated (such as stealing an authentication token, API keys etc.).
• Denial-of-service attacks.
• Self-XSS without a reasonable attack scenario.
• Injecting HTML to the emails which will be sent through Globbing.
• Fingerprinting on common/public services.
• Disclosure of known public files or directories (e.g robots.txt, sitemap.xml).
• Information disclosure without significant impact.
• SSL/TLS version and configuration issues, weak ciphers or expired certificates.
• Missing rate limits for non-critical actions.
• Cross-site Request Forgery (CSRF) with minimal security implications (e.g Login/Logout CSRF).
• SPF/DKIM/DMARC related issues.
• Missing or misconfigured security headers (e.g CSP, HSTS) which do not directly lead to a vulnerability.
• Missing Secure or HTTPOnly flags on cookies.
• Vulnerable software version disclosure without proof of exploitability.
• Reports from automated tools.
• Comma Separated Values (CSV) injection.
• EXIF metadata not being stripped from images.
• Brute-force attacks.
• Scenarios that require unlikely user interaction and/or outdated OS or software version.
• Broken link hijacking.
• Attacks requiring Man-in-the-middle (MITM) or physical access to a user's device.
• Bugs that do not pose any security risk.

• If our security team cannot reproduce or verify an issue, a report cannot be awarded.
• Please write your report in a way that makes it easier for us to reproduce the submitted issue.
• You must send a clear textual description of the vulnerability along with steps to reproduce the vulnerability.
• In order for the vulnerability report to be understandable and acceptable, you may include attachments such as screenshots or proof of concept code as necessary.
• List the related URL(s) and any affected parameters.
• Reports that only feature a video proof of concept without written reproduction steps will be refused.
• Don’t do more harm than good. You should not leave systems or users in a more vulnerable state than how you found them. You should not engage in testing or related activities that degrade, damage, or destroy information within our systems, or that may impact our users. While researching a vulnerability, if you are unsure whether you should continue, immediately engage with the Globbing Bug Bounty team (bugbounty@globbing.com).
• Please be patient while Globbing is working on the remediation process of the corresponding vulnerability. Refrain from asking for additional updates before 30 days have passed since your last response, as this will only increase our load and cause more delays.

• The quantity of affected users and data
• The sensitivity and classification of the affected data, and the security requirements surrounding it
• The impact on the affected data's confidentiality, integrity, or availability
• The privilege level required to exploit the vulnerability
• Whether user interaction is required to exploit the vulnerability
• Other, if any, mitigating factors or exploit scenario requirements