HackerOne Process

GitLab utilizes HackerOne for its bug bounty program. Security researchers can report vulnerabilities in GitLab applications or the GitLab infrastructure via the HackerOne website. Team members authorized to respond to HackerOne reports use procedures outlined here. The #hackerone-feed Slack channel receives notifications of report status changes and comments via HackerOne’s Slack integration.

Queues

  • New contains all reports in the New state
  • GitLab Team contains reports that have been validated by the HackerOne triage team, but are yet to be assigned to a specific GitLab team member
  • H1 Triage are reports being triaged by the HackerOne triage team
  • Pending Disclosure are reports that should be reviewed and disclosed

GitLab Team On-boarding

  • New members of the GitLab security team are granted access to the GitLab HackerOne team via an access request issue using the appropriate role based entitlement template, which should be submitted by their manager during onboarding
  • During onboarding, new GitLab security team members will be invited to join the HackerOne program if their role requires it.

Working the Queue

Namespace with Ultimate license for triaging

Please ensure that you use this namespace to create projects and groups required for testing vulnerabilities. This namespace is dedicated to reproduction of HackerOne issues.

HackerOne Triage Team

GitLab’s bug bounty program is managed by HackerOne. The HackerOne triage team are the first responders, and will work with researchers to validate reports before assigning to GitLab Team.

We usually trust the HackerOne Triage Team and don’t necessarily validate the report a second time. There are however cases when the GitLab team member on rotation may want to re-validate it, for example (non exhaustive list):

  • There may be additional impact that require more investigation
  • The severity can’t be properly assessed without further investigation

GitLab Team

  • When beginning work on a report, the security team member should assign the report to themselves immediately.

  • It is OK to take a report that you will not work on immediately, especially if it is a duplicate or related to another report you are familiar with, just be sure to get it reassigned if you won’t be able to meet the estimated triage time.

  • When starting a triage work cycle, team members should prioritize as follows:

    1. Identify, triage, and escalate any New severity::1/priority::1 issues first, from any queue.
    2. Close duplicate and invalid reports.
    3. Triage further using Sort by “Oldest” reports.
    4. Triage the GitLab Team queue.

    If a reporter has questions about the order of report responses, 06 - Duplicates/Invalid Reports Triaged First common response may be used.

  • Review the validation performed by the HackerOne triage team

  • Communicate with the reporter and investigate, using the following guidelines as necessary:

  • When a report contains externally-hosted static content for reproduction (for example some HTML file triggering a CSRF or a vulnerability exploiting a postMessage issue), follow the instructions in this project to re-host it internally

  • Potential, non-bounty outcomes:

    • Report is out-of-scope. If actionable, issues may still be created.
    • Report is a ~"type::feature" as defined above and would not need to be made confidential or scheduled for remediation. An issue can be created, or requested that the reporter creates one if desired, but the report can be closed as “Informative”.
    • Report is otherwise Informative, Not Applicable, or Spam. For example, we’ve gotten a number of reports for inline HTML in markdown that do not exceed the capabilities of markdown itself.
    • Report is a duplicate. Verify that the issue was not previously reported in HackerOne, or that an issue does not already exist in GitLab. If it is a duplicate:
      • Change the state of the report to “Duplicate”.
      • If the issue was previously reported in H1, include the report id, as it can impact the reporter’s reputation
      • Fill in the 01 - Duplicate common response. Include the link to the GitLab issue.
      • The team member may use their discretion if the reporter asks to be added as a contributor to the original H1 report; however, the default is to not add because the corresponding GitLab issue will be made public 30 days after the patch is released. If it is decided to add the duplicate reporter, ensure that the report does not have reporter sensitive information before allowing access. 05 - Duplicate Follow Up, No Adding Contributors/Future Public Release common response can be used when denying the request to add as a contributor.
      • If the new report makes us realize we have mishandled a previous report (e.g. closed as informative but it was a valid bug) we reopen the original and award the new report a bounty to thank the reporter for putting the mishandled issue back on our radar
        • The bounty we award as a thank you should be $100 for low severity reports and equivalent to the initial bounty we pay on triage for the higher severities
        • If we realize our mistake late in the process and we have already rewarded the new report, the bounty should be raised to the amounts above or left as is if it’s already higher
        • The author of the duplicate report should also be thanked in the CVE credits and blog post
        • If the new report demonstrates new and higher impact, we calculate the CVSS score and award to the new reporter the difference between the new severity and what was awarded to the original report

  • If the report relates to information disclosure, follow the triaging exposed secrets process.

  • If the report is valid, in-scope, original, and requires action, security-related documentation change, or if the report needs further investigation by the responsible engineering team:

    • Calculate the CVSS score and post the resulting vector string (e.g.: AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L) as an internal comment on the report, this will be used later when requesting a CVE ID
    • Verify and/or set the appropriate Severity in H1, using the CVSS previously calculated
      • Optionally explain the CVSS to the researcher, mention that CVSS scores are validated by a peer, and link to our Awards process to avoid inefficient misunderstandings relating to severity and payouts
    • Verify and/or set the appropriate Weakness in H1
    • If the report is permissions related, check for similar issues in the API, GraphQL, and Elasticsearch, as appropriate. Also check with alternate authentication mechanisms like Deploy Tokens, Deploy Keys, Trigger Tokens, etc.
    • Add your initial suggested bounty in H1
    • Import the report into a GitLab issue using /h1 import <report> [project] [options] in Slack
      • Note: by default a placeholder CVE issue is created and a brief note is added to the latest bug bounty council issue. Pass ~no-cve or ~no-bounty respectively to the /h1 import command to prevent their creation.
    • On the imported GitLab issue:
      • Verify the Severity/Priority assigned by h1import (Severity and Priority and Remediation SLAS)
      • Assign the appropriate Due Date
      • Have a proper How to reproduce section, by for instance copying the final reproduction steps written by our HackerOne triager into the issue.
      • If the report is a security-related documentation change, add the ~documentation label
      • @-mention the product manager and engineering manager based on the product categories page. Ask for engineering feedback if it is required to complete the triage
      • add labels (/label ~ command) corresponding to the DevOps stage and source group (consult the Hierarchy for an overview on categories forming the hierarchy)
      • As applicable, notify other relevant team members via the issue, chat, and email, depending on the chosen security level.
    • Change the state of the report to “Triaged” in HackerOne:
      • See GitLab’s H1 Policy, under Rewards, for portions of bounty rewards which are awarded at the time of triage
      • Choose from the following common responses:
        • 00 - Triaged pending further investigation for reports where the severity or validity is uncertain, and we are discussing with the engineering team.
        • 00 - Triaged for low severity reports, which do not have an initial bounty at the time of triage
        • 00 - Triaged with Bounty for medium, high, and critical reports which do have an initial bounty at time of triage
      • In the comment, include link to the confidential issue
    • Update the CVE issue and Bug Bounty Council note with relevant details, while they are still fresh in your mind
      • If the CVSS score is higher on GitLab.com than self-managed, calculate both scores and share them in the Bug Bounty Council issue. If the council agrees that security impact is higher on GitLab.com than self-managed, bounty award will be based on the CVSS for GitLab.com. The CVE and security release blog post will always use the self-managed CVSS.
      • Consider using the “Public description” field in the bug bounty council note. You can use the Duo-generated Public description that was created automatically if it is relevant and does not reveal too many details. This field will be picked up by the cve description update automation and used as the CVE description if present.
    • If you relied on the HackerOne Triage Team’s validation of the issue, consider setting time in your calendar to validate it yourself. This will help if you need to validate the fix later.
    • If full impact is needed to be assessed against GitLab infrastructure, instead of testing in https://gitlab.com, use https://staging.gitlab.com/help to sign in with your GitLab email account
      • If multiple users are needed, use credentials for users gitlab-qa-user* stored in 1password Team Vault to access the staging environment
    • If the report is for a bug that can be detected without authentication (in GitLab or anything else we host) consider reaching out to the Red Team or Vulnerability Management to help create a Nuclei template that we can include into our scanning

  • Remember to review the Pending Disclosure tab and follow our disclosure process

Calculating CVSS for Vulnerability Chaining

Typically, each HackerOne report discloses a single vulnerability. However, sometimes a single report uses two or more newly discovered vulnerabilities chained together for increased impact.

When a single report discloses two or more new vulnerabilities being chained together for greater impact, calculate the CVSS for each individual vulnerability and an additional “vulnerability chaining” CVSS score for the combined impact. Share both the individual CVSS scores and the “vulnerability chaining” CVSS score in the corresponding bug bounty council issue.

The CVSS of each individual vulnerability will be used for the CVEs issued for each vulnerability. The “vulnerability chaining” CVSS will be used to determine bounty award for the report.

For future reports that involve “vulnerability chaining” with previously disclosed vulnerabilities, only calculate the CVSS for newly disclosed vulnerabilities. In such cases, only the new vulnerabilities in the chain will be eligible for a “vulnerability chaining” CVSS-based bounty.

Triaging exposed secrets

Click to view copy-pastable Appsec Triage Checklist markdown to help with triaging exposed secrets 
### Appsec Triage checklist
- [ ] Mitigate the incident if possible
  - [ ] If the exposed secret is a Agent Token:
    - [ ] Validate if the token is a valid one by following the steps [here](https://gitlab.com/gitlab-com/gl-security/security-research/verify-kas-token#testing-kas-token-for-validity) and gather the output for the SIRT incident.
    - [ ] [Reset the token](https://docs.gitlab.com/ee/user/clusters/agent/work_with_agent.html#reset-the-agent-token) and reach out to the owner of the token through Slack DM and in the SIRT issue that you will create in the steps below.
  - [ ] If the exposed secret is a Personal Access Token:
    - [ ] Using the API, gather the output of [`/api/v4/user`](https://docs.gitlab.com/ee/api/users.html#for-normal-users-1) and [`/api/v4/personal_access_tokens/self`](https://docs.gitlab.com/ee/api/personal_access_tokens.html#using-a-request-header) for the SIRT incident.
    - [ ] [Revoke the token](https://docs.gitlab.com/ee/api/personal_access_tokens.html#using-a-request-header-1) and reach out to the owner of the token through Slack DM and in the SIRT issue that you will create in the steps below.
  - [ ] Post a comment in `#security-revocation-self-service` using [this message template](https://gitlab.com/gitlab-com/gl-security/security-operations/sirt/runbooks/-/blob/main/misc/exposed_secrets.md#general-revocation-template-for-secrets)
  - [ ] If the information was leaked in an issue, make the Issue confidential and leave an internal note explaining why it's been made confidential.
- [ ] Use the `/security` slack command to [initiate](/handbook/security/security-operations/sirt/engaging-security-on-call/#engage-the-security-engineer-on-call) an incident
  - [ ] In the description section, include a link to the HackerOne report and any other useful information
    - [ ] Share the reporter's IP address(es) and time(s) the reporter accessed the sensitive data to assist with incident response.
  - [ ] In the remediation section, document what time and from what IP used to revoke the token or validate the leak.
  - [ ] If in doubt, choose "Urgent".
  - [ ] If you've been able to mitigate the incident, choosing "Not Urgent" is fine. The SEOC typically responds quickly anyway.
- [ ] Add information to the SIRT issue.
  - [ ] Update the Timeline section to include the date the secret was leaked, when HackerOne report came in, and when you took any actions.
  - [ ] Add any comments to the SIRT issue with context or information that might be helpful.
- [ ] In the H1 report use the reference field to link to the SIRT issue (for example if the incident issue is `https://gitlab.com/gitlab-sirt/incident_XXXX/-/issues/1` the reference should be `gitlab-sirt/incident_XXXX/-/issues/1`)
- [ ] Identify the most appropriate [non-CVSS bounty amount](https://gitlab-com.gitlab.io/gl-security/product-security/appsec/cvss-calculator/) and add your initial [suggested bounty](https://docs.hackerone.com/en/articles/8524543-bounties#h_13d3d2c2b7) in H1
- [ ] Use `/h1 bounty REPORT_ID` to create a comment on the Bug Bounty Council issue (this step should not be necessary if `/h1 import` was previously run without the `~no-bounty` option.)
- [ ] Support SIRT as required and, if applicable, follow the process for [handling severity::1/priority::1 issues](handling-s1p1.html)
- [ ] Investigate the location of the exposure, and locations like it, for further exposure.
  - [ ] Check the history on issue / MR descriptions
  - [ ] Check git commit history
  - [ ] Check build artifacts
  - [ ] Use Advanced Search to look for similar patterns in other projects used by GitLab team members
- [ ] If it was leaked through GitLab Unfiltered, add the report to the [tracking issue](https://gitlab.com/gitlab-com/gl-security/security-research/video-scanner/youtube-video-scanner/-/issues/17)

Exposure of information and secrets is handled a little differently to vulnerabilities, as there is nothing to patch and therefore no need for a GitLab Project Issue, CVSS, or CVE. When a leak occurs:

  • Mitigate the incident if possible
    • If the exposed secret is a Agent Token:
      • Validate if the token is a valid one by following the steps here and gather the output for the SIRT incident.
      • Reset the token and reach out to the owner of the token through Slack DM and in the SIRT issue that you will create in the steps below.
    • If the exposed secret is a Personal Access Token:
    • Post a comment in #security-revocation-self-service using this message template
    • If the information was leaked in an issue, make the Issue confidential and leave an internal note explaining why it’s been made confidential.
  • Use the /security slack command to initiate an incident
  • Add information to the SIRT issue.
    • Update the Timeline section to include the date the secret was leaked, when HackerOne report came in, and when you took any actions.
    • Add any comments to the SIRT issue with context or information that might be helpful.
  • In the H1 report use the reference field to link to the SIRT issue (for example if the incident issue is https://gitlab.com/gitlab-sirt/incident_XXXX/-/issues/1 the reference should be gitlab-sirt/incident_XXXX/-/issues/1)
  • Identify the most appropriate non-CVSS bounty amount and add your initial suggested bounty in H1
  • Use /h1 bounty REPORT_ID to create a comment on the Bug Bounty Council issue (this step should not be necessary if /h1 import was previously run without the ~no-bounty option.
  • Support SIRT as required and, if applicable, follow the process for handling severity::1/priority::1 issues
  • Investigate the location of the exposure, and locations like it, for further exposure.
    • Check the history on issue / MR descriptions
    • Check git commit history
    • Check build artifacts
    • Use Advanced Search to look for similar patterns in other projects used by GitLab team members
  • If it was leaked through GitLab Unfiltered, add the report to the tracking issue

Triaging exposed personal data

Similar to how we handle exposed secrets, we sometimes handle exposed personal data which also doesn’t need a GitLab Project Issue, CVSS or CVE.

  • Mitigate the incident if possible
    • If the information was leaked in an issue, make the Issue confidential and leave an internal note explaining why it’s been made confidential.
    • ⚠️ Bear in mind that turning an issue confidential doesn’t turn attachments confidential.
  • Use the /security slack command to initiate an incident
  • Add information to the SIRT issue.
    • Add any comments to the SIRT issue with context or information that might be helpful.
  • In the H1 report use the reference field to link to the SIRT issue (for example if the incident issue is https://gitlab.com/gitlab-sirt/incident_XXXX/-/issues/1 the reference should be gitlab-sirt/incident_XXXX/-/issues/1
  • Identify the most appropriate non-CVSS bounty amount and add your initial suggested bounty in H1
  • Use /h1 bounty REPORT_ID to create a comment on the Bug Bounty Council issue
    • Note that we are importing it using bounty only here.
  • Support SIRT as required and, if applicable, follow the process for handling severity::1/priority::1 issues
  • Investigate the location of the exposure, and locations like it, for further exposure.
    • Check the history on issue / MR descriptions
    • Use Advanced Search to look for similar patterns in other projects used by GitLab team members

Triaging features behind a feature flag

Sometimes researchers will report a vulnerability in features behind a feature flag. These reports are excellent as they allow us to patch vulnerabilities prior to them affecting our wider audience that utilizes the default settings. These reports are eligible for the full amount of their calculated bounty.

Pay attention to the full report to determine the Attack Complexity. The word complex in the bullet points below is as defined in the section 2.1.2 Attack Complexity in CVSS 3.1 Specification. Keep in mind, the aforementioned section says the following under the 2.1.2 Attack Complexity section - “If a specific reasonable configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.”.

  • A vulnerability in a feature behind a feature flag that is not complex will be paid out at AC:L (this is after assuming the feature flag is enabled on a vulnerable instance). However we will handle the report as if it’s AC:H for triage and SLOs.
  • A vulnerability in a feature behind a feature flag that is quite complex will still be AC:H (this is after assuming the feature flag is enabled on a vulnerable instance)

Vulnerabilities behind disabled-by-default feature flags do not need a CVE (use ~no-cve when importing) as they are patched in regular releases, not security releases.

Triaging issues in lower Ruby versions

Some vulnerabilities will only work on certain Ruby versions. In order to reproduce them locally using GDK, here is how you can change your Ruby version:

  1. Update the Ruby version inside the following file to the required version:
    • gitlab-development-kit/.tool-versions
    • gitlab-development-kit/gitlab/.tool-versions
  2. Run asdf install ruby <required-version> while inside the GDK directory.
  3. Run gem install gitlab-development-kit while inside the GDK directory.
  4. Go into the ./gitlab directory inside the GDK direcory, and run bundle install.
  5. Verify the Ruby version after running gdk restart and going to https://127.0.0.1:3000/admin

Triaging deprecated features

Vulnerabilities in deprecated features are triaged normally. See discussion for more information.

Triaging DNS record takeovers

DNS record takeovers typically require multiple teams in order to triage. The workflow is slightly different:

  • Instead of pinging the team responsible for the given page (or service, in the case of MX or TXT records) we collaborate with SIRT and the SRE Oncall
  • We import the HackerOne report to the infrastructure repository via /h1 import $REPORT infrastructure
  • Engage SIRT via /security in Slack. This will allow SIRT to perform their investigatory duties related to this type of attack.
  • Engage @sre-oncall in Slack. This notifies the SRE (but does not intiate a PagerDuty ping) on-call of a situation requiring their attention. In the relevant SIRT issue, the responder should be added to the issue by the GitLab SIRT. Remediation of this vulnerability happens within the SIRT issue and typically involves deleting the dangling CNAME record. For issues involving MX record takeovers we typically work with our MX SaaS vendor, Mailgun to obtain control of the record. More information on MX record takeovers can be found here.

Awards

  • See GitLab’s H1 Policy, under Rewards, for portions of bounty rewards which are awarded at the time of triage
    • It is OK to delay awarding at time of triage. Examples are when we aren’t sure if a report is intended behaviour, or if it will be a documentation change. Remember to return and make a partial award if/when appropriate.
    • It is OK to have awarded a partial bounty at time of triage and later learn we have overpaid due to an adjustment of validity or severity
  • If the report does not already have a council issue, use the /h1 bounty <report> Slack bot to post a note on the current ~“bug bounty council” issue
    • Add descriptions, similar issues, and other commentary as appropriate
  • Award approval:
    • For documentation updates, an award can be paid immediately
    • For Low and Medium CVSS, an award can be paid after at least one team member reacts with a thumbsup emoji
    • For High and Critical CVSS, two team members must react with a thumbsup emoji on the note
    • If needed, make a request in #sec-appsec when your note has not received enough votes
  • After Bug Bounty Council approval:
    • Consider explaining the CVSS score and council discussion points on the canonical issue. This helps teams understand the severity during remediation and, when the issue becomes public, it gives transparency to researchers and customers on how we reached a given score.
    • If 30 days have passed since the issue was triaged, the approved award may be paid in advance of a confirmed fix using the 04 - Bounty Award / Reviewed and Awarded Prior to Fix common response.
    • Once a fix is shipped, award the remaining amount (or full amount if none was awarded at time of triage) using the 02 - Bounty Award common response
    • Add a 💰 emoji to the bug bounty council thread after paying the bounty award.

We can award GitLab swag to reporters who have submitted a quality report that did not qualify for a monetary reward in our Bug Bounty program. To award swag, please follow the swag nomination process that is managed by our Developer Relations team.

We can also request to plant trees in the GitLab Forest as a non-monetary rewards, where reporters for various reasons can’t accept swag or a monetary award. The amount varies based on the severity, please add a note in the request form based on the list here (Internal link).

Managing issues

Discussion and remediation of vulnerabilities can sometimes take longer than we would prefer. Even so, frequent communication with reporters is far better than leaving reporters in the dark, even if our progress is slow. Therefore:

  • Once the corresponding GitLab issue has been assigned a milestone, an automated process will add a comment to the H1 report with the planned fix date. If the issue has not been assigned to a milestone within 1 week of the product manager being @ mentioned on the issue, follow up with the product management team.
  • In the case where fixes are not as clear or discussion is still on-going as to whether a patch will be created at all, reporters should be notified of updates at least monthly.
  • In any case, no report should go “stale” where updates are not provided within the last month.

SLA exceptions

The HackerOne bot will automatically assign the correct due date based on severity of the imported issue. However, sometimes the issues may for various reasons not be patched within that timeframe. When this happens, development teams should open a SLA exception and have it approved by the Vulnerability Management team. The Application Security team is available to assist by providing guidance on these exception requests, but the expectation is that development teams will submit these requests and provide the justification and exception type.

Closing out & disclosing issues

When a patch is released and the award process complete, it is time to close the HackerOne issue.

After 30 days, follow the process for disclosing security issues. Once this has occurred, the HackerOne issue can also be publicly disclosed on a case-by-case basis, following the same process to remove sensitive information. We should not disclose, or request to disclose, a HackerOne issue while the GitLab issue remains confidential.

Comments made by GitLab Security Bot (@gitlab-securitybot) can be redacted by AppSec or SecAuto team members using the /h1 redact <comment_url> Slack command.

To create a HackerOne Hactivity page which will help other researchers learn more about quality reporting we welcome disclosure of resolved reports which are unique and interesting.

If a researcher requests public disclosure of a closed non-resolved report (e.g. Informative or Not Applicable), we opt to cancel disclosure requests using the 08 - Canceled Disclosure Message template. Reporters should instead consider opening a public GitLab issue as this is the best way to raise and address non-vulnerability issues.

If a researcher insists on disclosure via HackerOne we should agree to disclose it regardless of quality unless there is a good reason not to.

Application Security Engineer Procedures for severity::1/priority::1 Issues

Please see Handling severity::1/priority::1 Issues

Closing reports as Informative, Not Applicable, or Spam

If the report does not pose a security risk to GitLab or GitLab users it can be closed without opening an issue on GitLab.com.

When this happens inform the researcher why it is not a vulnerability. It is up to the discretion of the Security Engineer whether to close the report as “Informative”, “Not Applicable”, or “Spam”. HackerOne offers the following guidelines on each of these statuses:

  • Informative: Report contained useful information but did not warrant an immediate action.
  • Not Applicable: Report was invalid, ineligible, or irrelevant.
  • Spam: Report is not a legitimate attempt to describe a security issue.

We mostly use the “Informative” status for reports with little to no security impact to GitLab and “Not Applicable” for reports that show a poor understanding of security concepts or reports that are clearly out of scope. “Spam” results in the maximum penalty to the researcher’s reputation and should only be used in obvious cases of abuse.

It may be appropriate to suggest opening a public GitLab Issue for reproducible bugs that are not vulnerabilities.

If a Report is Unclear

If a report is unclear, or the reviewer has any questions about the validity of the finding or how it can be exploited, now is the time to ask. Move the report to the “Needs More Info” state until the researcher has provided all the information necessary to determine the validity and impact of the finding. Use your best judgement to determine whether it makes sense to open a confidential issue anyway, noting in it that you are seeking more information from the reporter. When in doubt, err on the side of opening the issue.

One the report has been clarified, follow the “regular flow” described above.

Breakdown of Effective Communication

Sometimes there will be a breakdown in effective communication with a reporter. While this could happen for multiple reasons, it is important that further communication follows GitLab’s Guidelines for Effective and Responsible Communication. If communication with a reporter has gotten to this point, the following steps should be taken to help meet this goal.

  • Take a step back from the situation. Do not respond immediately.
  • Seek advice from the H1 triage engineer or, if you are more comfortable, a manager on how best to move forward.
  • Consider writing the response multiple times, and have the response reviewed by the person you consulted.
  • Once diffused, if the general situation is not currently documented, open an MR to the handbook on how it can be handled in the future.

If the situation leads to a code of conduct violation, follow the process for addressing Code of Conduct violations.

Addressing Rules of Engagement or Code of Conduct violations

When behavior violates our Rules of Engagement or HackerOne’s Code of Conduct we use the Bug Bounty Council to discuss, agree on, and document our response. Add a comment to the current Bug Bounty Council Issue using the template found in the issue description.

In line with our Transparency value, we should try to explain to the researcher why we’ve taken action and what those actions were. However in some instances (e.g. program bans) it may be appropriate to let HackerOne handle all communication, to keep our team members safe from potential abuse or retribution.

Reports potentially affecting third parties

When GitLab receives reports, via HackerOne or other means, which might affect third parties the reporter will be encouraged to report the vulnerabilities upstream. On a case-by-case basis, e.g. for urgent or critical issues, GitLab might proactively report security issues upstream while being transparent to the reporter and making sure the original reporter will be credited. GitLab team members however will not attempt to re-apply unique techniques observed from bug bounty related submissions towards unrelated third parties which might be affected.

Vulnerabilities on third-party software are accepted according to the following rules, as stated in our HackerOne policy: The report includes a new vulnerability, for which a patch is not available, or

  • A patch has been available for more than 30 days.
  • It has a clear and working proof of concept that illustrates the impact to GitLab.
  • It has Critical or High impact to GitLab.

This does not include websites of third party software and services and only includes dependencies & packaged software.

Awarding Ultimate Licenses

GitLab reporters with 3 or more valid reports are eligible for a 1-year Ultimate license for up to 5 users. As per the H1 policy, reporters will request the license through a comment on one of their issues. When a reporter has requested a license, the following steps should be taken:

  1. Validate that the three reports were valid. That means they are Triaged or Resolved.
  2. Validate that the three reports have not been used to obtain a previous license.
  3. If the reports are not valid, respond to the reporter on H1 explaining the reason the license is not being issued.
  4. If the reports are valid, visit the GitLab Support Internal Requests page and use the GitLab Support Internal Requests for Global customers request option, then select Hacker One Reporter license for the internal request type.
    • For Contact Name use the reporter’s full name if available, otherwise their H1 handle
    • For Contact Email use the reporter’s [username]@wearehackerone.com email address
  5. Enter the associated license information in the H1 License Award sheet
  6. Reply to the report on H1 use the 20 - Ultimate License Creation template.

The license will be sent to the reporter by CustomersDot. If the reporter claims that the license has not arrived, the app can be used to resend the license. When that happens, the creation of a new license should be avoided.

Questions?

Members of the public can ask questions about our HackerOne bug bounty program here: https://gitlab.com/gitlab-com/gl-security/product-security/appsec/hackerone-questions/. Note that this repository is not the place to discuss or disclose reports and vulnerabilities.

HackerOne Triage Team GitLab licenses

All members of the HackerOne triage team have access to GitLab Ultimate licenses. HackerOne will inform us annually when the license needs to be renewed.

  • Visit the GitLab Support Internal Requests page
  • Use the GitLab Support Internal Requests for Global customers request option, then select Hacker One Reporter license for the internal request type.
  • Paste the following:
Two new licenses are needed for our HackerOne Triage+ team. This team helps us triage HackerOne reports and will need at least two licenses with 50 users each. They need ultimate licenses to validate reports affecting any feature of the product.

License 1: `analysts@managed.hackerone.com`

License 2: `analysts+1@managed.hackerone.com`

Company: HackerOne Inc.

License type: Ultimate

Number of users for each license: 50

License duration: 1 year
Last modified December 16, 2024: Update file hackerone-process.md (8e5b1ace)
View page source - Edit this page - please contribute. Creative Commons License