Bugcrowd

Description

Bugcrowd orchestrates the creativity of the crowd to solve some of cybersecurity's toughest challenges. Our own security is our highest priority. If you think you’ve found a security vulnerability in our systems, we invite you to report it to us via our platform. We commit to working with you to get it assessed and handled appropriately, and offer cash rewards for valid, unique vulnerability reports. This program is for reporting potential security vulnerabilities only. If you want to report a functional bug, require assistance with a submission, or have a general question, please visit our contact page . We’ve set up a bounty on the Bugcrowd platform called Hack Me! , where you’re welcome to hack as if on a customer’s bounty. Please do not ever test against a real customer’s bounty. As stated in our code of conduct , disruptive testing which affects other Researchers’ access to the testing environment, or adversely impacts a customer’s systems and/or accounts is prohibited. Our bounty program adheres strictly to Bugcrowd’s Vulnerability Rating Taxonomy – a collaborative, community-driven effort to classify common security vulnerabilities and identify baseline severity ratings based on real findings across hundreds of bug bounty programs. Before submitting your vulnerability, consult the VRT to determine its severity and whether it may be eligible for a reward. Vulnerabilities with a P5 baseline rating according to the VRT are generally not eligible for a bounty. If you’d like to make a suggestion to improve the VRT, you can create an issue on GitHub . Bonuses When presented with especially interesting High (P2) or Critical (P1) Priority vulnerabilities – especially if our internal knowledge allows us to identify a much greater impact than what an outside researcher's proof-of-concept may have suggested on its own – we may choose to award an additional bonus amount of up to 100% of the initial reward suggested by our priority guidelines. Such bonuses are always at our discretion.

Targets

We are most interested in vulnerabilities on our core platform and infrastructure, which run on Amazon Web Services. However, if you identify a host not listed in the Targets section that you can reasonably demonstrate belongs to Bugcrowd, feel free to submit a report asking about its eligibility. Such reports will not result in a penalty, even if it turns out that the given target is ineligible. If deemed eligible, reports against such targets will be assessed on a case-by-case basis. Authenticated testing is limited to whatever credentials you can self provision - no supplemental credentials or access will be provided for testing. Excluded Submission Types Vulnerability reports lacking manual validation, such as those solely reliant on automated tools and scanners, or those that describe theoretical attack vectors without substantiated proof of exploitability, will be classified as "Not Applicable". Rate Limiting EXIF data not stripped from file attachments on Submissions github.com/bugcrowd.com PRs, Issues unless the finding revolves around credential leakage or critical impact Prompt Injection vulnerabilities Out of Scope Submissions outlining the ability for a researcher to set their username to match the format used by Bugcrowd Staff, Customers and ASE team are Out of Scope. The username alone has no effect in user permissions on our platform. adding any variation of _bugcrowd to the username for normal users Non-Rewardable Targets Our approach to rewarding vulnerabilities is based on implementing code changes. In the case of a 3rd party system where the code change falls outside our reach to fix if the vulnerability will not be up for a cash prize. Specific areas include: 3rd party services listed below We reserve the right to, provide rewards for exceptionally impactful and informative submissions, even if they are targeting assets that are not typically eligible for rewards. However, the highest payouts will be reserved for the explicitly listed in-scope targets. Third-party services Bugcrowd uses a number of third-party providers and services. We cannot authorize security testing against systems that do not belong to us, but strongly suggest reporting issues identified within these services to the third-party directly: Out-of-scope target │ Company │ Report via www.bugcrowd.com, blog.bugcrowd.com │ Pantheon │ Pantheon Bug Bounty Cloudflare │ Cloudflare Bug Bounty Drift │ Email Intercom │ Intercom Bug Bounty forum.bugcrowd.com │ Discourse │ Discourse Bug Bounty email.bugcrowd.com, email.forum.bugcrowd.com │ Mailgun │ Contact collateral.bugcrowd.com │ Outreach │ Outreach Bug Bounty bounce.bugcrowd.com, go.bugcrowd.com, ww2.bugcrowd.com │ Marketo │ Email pages.bugcrowd.com │ Hubspot │ Hubspot Bug Bounty researcherdocs.bugcrowd.com │ Readme.io │ Email events.bugcrowd.com │ Splash │ Email assetinventory.bugcrowd.com │ BitDiscovery │ BitDiscovery bugcrowd.freshdesk.com │ Freshdesk │ Freshdesk bugcrowd-support.freshdesk.com support widget │ Freshdesk │ Freshdesk github.com/bugcrowd PRs, Issues etc │ -- │ unless the finding revolves around credential leakage or critical impact trust.bugcrowd.com │ Safebase All Jumio related endpoints │ Jumio (NetVerify) │ Jumio VDP However, if you believe an issue with one of our third-party service providers is the result of Bugcrowd's misconfiguration or insecure usage of that service, we'd appreciate your report regarding the issue. Past and Present Employees Bugcrowd Employees can participate in our own internal program, but are subject to our Employee Participation policies. These policies can be found on our internal wiki - if in doubt contact our internal program administrators. Thanks and props to our past employees who are out bounty-hunting! There is a 30-day exclusion cooldown on your participation in this program. We will not accept submissions from you until 30 days after you've left the company, to minimise conflicts of interest. Safe Harbor When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our official channels before going any further.

Additional information

This program requires explicit permission to disclose the results of a submission.

In Scope Targets (in scope)

Disclaimer: Government (.gov) targets may not be publicly accessible at this time.

Beta Feature Target (in scope)

Our engineering team is working on migrating the platform to use centralized authentication and we appreciate the help of our researchers to test this beta feature! Please note not everyone may have access to the endpoint. In addition reports are subject to be duped to internal ones. This feature is subject to different rewards than our main program

Out of scope targets (out of scope)

Other domains/assets owned by Bugcrowd but not listed, are not in scope and are ineligible for bounty