Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:GitLab
Status
Severity
Weakness
Year:2017
Clear
Bounty paid0
Access stated
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters29 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Access to GitLab's Slack by abusing issue creation from e-mail#218230ValidAuthentication–2017-09-21–54
Race condition in GitLab import, giving access to other people their imports due to filename collision#214028ValidInformation Disclosure–2017-10-03–22
Gitlab is vulnerable to impersonation attacks due to broken links#265696ValidMisconfiguration and Insecure Design–2017-09-06–21
[Markdown] Stored XSS via character encoding parser bypass#270999ValidCross-site Scripting–2017-10-18–20
all private tokens are leaked to an unauthenticated attacker#268794ValidAccess Control–2017-09-21–20
CSV injection in gitlab.com via issues export feature.#216243ValidCommand and Code Injection–2017-07-21–20
SSRF vulnerability in gitlab.com via project import.#215105ValidServer-Side Request Forgery–2017-11-09–20
Stored XSS on Files overview by abusing git submodule URL#218872ValidCross-site Scripting–2017-05-09–17
User with guest access can access private merge requests#195134ValidAccess Control–2017-01-23–13
Impersonation attack via Broken Link in Resellers Page#266908ValidMisconfiguration and Insecure Design–2017-09-08–12
Every user can delete public deploy keys#195088ValidAccess Control–2017-01-23–12
Unfiltered `class` attribute in markdown code#216453ValidCross-site Scripting–2017-04-13–11
[Subgroups] Unprivileged User Can Disclose Private Group Names#215384ValidInsecure Direct Object Reference–2017-03-30–11
Users can download old project exports due to unclaimed namespace#195058ValidInformation Disclosure–2017-01-23–10
Users with guest access can post notes to private merge requests, issues, and snippets#195140ValidAccess Control–2017-01-23–9
Markdown based stored XSS (IE only)#118024ValidCross-site Scripting–2017-05-03–9
Gitlab.com is vulnerable to reverse tabnabbing. (#2)#212629ValidMisconfiguration and Insecure Design–2017-05-09–8
Gitlab.com is vulnerable to reverse tabnabbing.#211065ValidOpen Redirect–2017-03-21–8
[RDoc] XSS in project README files#200693ValidCross-site Scripting–2017-02-15–8
[reStructuredText] XSS in project README files#205497ValidCross-site Scripting–2017-02-15–7
CSRF Token Bypass in Account Deletion#182487ValidCross-Site Request Forgery–2017-04-20–7
CSRF-Token leak by request forgery#221432ValidCross-Site Request Forgery–2017-10-09–6
GFM renderer leaks external issue tracker URL of private project#133717ValidInformation Disclosure–2017-06-08–6
Gitlab.com is vulnerable to reverse tabnabbing via AsciiDoc links. (#3)#213114ValidMisconfiguration and Insecure Design–2017-05-09–5
[Textile] XSS in project README files#205498ValidCross-site Scripting–2017-02-15–5
[Repository Import] Open Redirect via "continue[to]" parameter#215970ValidOpen Redirect–2017-04-06–4
Open redirect#214034ValidOpen Redirect–2017-04-06–4
SSRF via git Repo by URL Abuse#191216DuplicateServer-Side Request Forgery–2017-11-28–3
Missing/Breach of Internal Security Boundary - Access to Job Queue Results in Remote Code Execution#224198InformativeMisconfiguration and Insecure Design–2017-06-28––

Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (227 analysed so far), which can be wrong. Data as of 2026-11-14.

Updated AboutDevelopersSign in