<!---
Please read this!

This template is for reporting a security vulnerability about GitLab or 
GitLab.com

If you are eligible to participate in our bug bounty program, please
report via https://hackerone.com/gitlab instead. HackerOne is our
preferred platform for vulnerability disclosures and allows you to be
recognized and rewarded for your findings.
This issue tracker remains available for reporters who are not
eligible for the bug bounty (e.g. GitLab team members or otherwise ineligible
for the bug bounty program), or who would
rather disclose here, keeping in mind that submissions through the
issue tracker are not eligible for a HackerOne bounty.

See also:

- https://about.gitlab.com/security/disclosure/
- https://about.gitlab.com/handbook/engineering/security/#creating-new-security-issues
- https://about.gitlab.com/handbook/engineering/security/#engaging-the-security-on-call

--->

> **Preferred reporting channel:** If you are eligible to participate in our [bug bounty program](https://hackerone.com/gitlab), please report via [HackerOne](https://hackerone.com/gitlab) instead of this issue tracker. HackerOne is our preferred platform for vulnerability disclosures. Eligibility terms are described on our policy there.

- [ ] I understand that submitting this vulnerability through the GitLab issue tracker makes it ineligible for a bounty through [HackerOne](https://hackerone.com/gitlab).

⚠ Please read the [process](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/security/engineer.md) on how to fix security issues before starting to work on the issue. Vulnerabilities must be fixed in a security mirror.

### Summary

<!-- Summarize the bug encountered concisely. -->

### Steps to reproduce

<!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. -->

### Example Project

<!-- If possible, please create an example project here on GitLab.com that exhibits the problematic 
behavior, and link to it here in the bug report. If you are using an older version of GitLab, this 
will also determine whether the bug is fixed in a more recent version. -->

### What is the current *bug* behavior?

<!-- Describe what actually happens. -->

### What is the expected *correct* behavior?

<!-- Describe what you should see instead. -->

### Relevant logs and/or screenshots

<!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
 as it's tough to read otherwise. -->

### Output of checks

<!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com -->

#### Results of GitLab environment info

<!--  Input any relevant GitLab environment information if needed. -->

<details>
<summary>Expand for output related to GitLab environment info</summary>

<pre>

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

</pre>
</details>

#### Results of GitLab application Check

<!--  Input any relevant GitLab application check information if needed. -->

<details>
<summary>Expand for output related to the GitLab application check</summary>
<pre>

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)

(we will only investigate if the tests are passing)

</pre>
</details>

### Possible fixes

<!-- If you can, link to the line of code that might be responsible for the problem. -->


---

<!-- Do not edit past here unless you are certain of the impact -->

cc @gitlab-com/gl-security/product-security/psirt-group 

/label ~"type::bug" ~"bug::vulnerability"
/label ~"PSIRT"
/confidential
