IndiaMART bug bounty program is our way to reward security researchers for finding serious security vulnerabilities in our core application indiamart.com. Please report any vulnerabilities with full details to email@example.com.
The scope of the bug bounty program is limited to the vulnerability listed under in scope. Valid vulnerabilities on any indiamart.com domain which are not explicitly listed in the scope will be accepted but shall be ineligible for a bounty reward. For example, vulnerabilities on any indiamart.com properties not listed below will not be awarded a bounty unless impact on indiamart.com security posture can be demonstrated.
All software components that are used within the indiamart.com application may be exploited in your attack. Please note that bugs in third party components only qualify if you can prove that they can be used to successfully attack our systems or applications. Reports having genuinity and consisting of actual security or privacy impact shall be rewarded.
For Bounty eligible assets, indiamart.com default policy is to award the bounty after our Technical and Security Team confirms the issue during the Triage process. We generally won't wait to award a bounty until the item is fixed,however, we may make an exception to this policy on a report-by-report basis as and when we deem fit.
If you need further clarification of the rules or scope of our bug bounty program, you may email us at firstname.lastname@example.org.
Bounty Amounts Calculations:
Bounty amounts will be determined using our CVSS Bounty Calculator. In most cases, we will only triage and reward vulnerabilities with a CVSS score greater than 0.
- Do not run automated scans without checking with us first.
- Do not test the physical security of indiamart.com offices, employees, equipment, etc.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Do not perform DoS or DDoS attacks.
- In any way, attack our end users, or engage in trade of stolen user credentials.
- Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
- You must disclose all possible ways to exploit an issue in your original report. indiamart.com will not issue a bounty, follow-on bounty, or bonus if we believe you are abusing the report system by not providing complete information in your initial report.
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward. This usually requires a working proof-of-concept typically in the form of a clickable link that we can verify. Videos or screenshots are not considered definitive proof.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
- If you are a IndiaMART employee or are related to an employee (parent, sibling, spouse), you are not eligible for the bounty bug program
- If you are a IndiaMART customer or a security researcher interested in making our systems safe, you are eligible
- Bounties are issued solely at the discretion of indiamart.com.
- Indiamart.com and its sub-domain
- Our mobile sites - m.indiamart.com
- Our mobile apps - Android & iOS
- Broken Authentication (including OAuth bugs)
- Broken Session flaws
- Code Executions
- Server Side Request Forgery (SSRF)
- Privilege Escalations
- Authentication Bypasses
- File inclusions (Local & Remote)
- Misuse/Unauthorized use of our APIs
- Improper TLS protection
- Leakage of sensitive data
- Directory Traversal
- Payment manipulation
- Open Redirects (With significant security impact)
Out of Scope:
- Vulnerabilities affecting users of outdated browsers or platforms
- Any kind of Data breach activities
- Any hacker activities for the purpose of disruption of service.
- Missing HTTP security headers, specifically OWASP Headers
- Issues that require unlikely user interaction
- Best practices/issues
- Unverified Results of automated tools or scanners
- Issues related to networking protocols or industry standards
- Cross-Site Scripting (XSS).
- Cross-Site Request Forgery (CSRF)
- SQL Injection
- Unsecured S3 buckets
- Out of Scope bugs for Android
- Absence of certificate pinning
- Sensitive data stored in app private directory
- User data stored unencrypted on external storage
- Lack of binary protection control in android app
- Shared links leaked through the system clipboard.
- Any URIs leaked because a malicious app has permission to view URIs opened
- Sensitive data in URLs/request bodies when protected by TLS
- Lack of obfuscation
- oauth &#;app secret#; hard-coded/recoverable in apk
- Crashes due to malformed Intents sent to exported Activity/Service/BroadcastReceive (exploiting these for sensitive data leakage is commonly in scope)
- Out of Scope bugs for IOS
- Absence of certificate pinning
- Lack of Exploit mitigations i.e., PIE, ARC, or Stack Canaries
- Path disclosure in the binary
- User data stored unencrypted on the file system
- Lack of binary protection (anti-debugging) controls
- Lack of obfuscation
- Lack of jailbreak detection