- Dec 13, 2019
-
-
GitLab Release Tools Bot authored
[ci skip]
-
John Skarbek authored
Install lsb-release for repo URL construction See merge request gitlab/gitlabhq!3592
-
Kyle Wiebers authored
-
John Skarbek authored
-
John Skarbek authored
This reverts commit e29a2ba5.
-
John Skarbek authored
This reverts commit dda1b34c.
- Dec 12, 2019
-
-
GitLab Release Tools Bot authored
[ci skip]
-
John Skarbek authored
-
John Skarbek authored
This reverts commit 426287d2.
-
John Skarbek authored
This reverts commit fb3833cd.
- Dec 11, 2019
-
-
GitLab Release Tools Bot authored
[ci skip]
- Dec 10, 2019
-
-
John Skarbek authored
Backport reliable fetcher to 12.2 See merge request gitlab/gitlabhq!3585
-
- Dec 09, 2019
-
-
Valery Sizov authored
- Oct 30, 2019
-
-
GitLab Release Tools Bot authored
-
- Oct 28, 2019
-
-
GitLab Release Tools Bot authored
[ci skip]
- Oct 25, 2019
-
-
GitLab Release Tools Bot authored
Return 404 on LFS request if project doesn't exist See merge request gitlab/gitlabhq!3508
-
Igor Drozdov authored
-
- Oct 24, 2019
-
-
GitLab Release Tools Bot authored
Only assign merge params when allowed See merge request gitlab/gitlabhq!3460
-
GitLab Release Tools Bot authored
Nested GraphQL query with circular relationship can cause Denial of Service See merge request gitlab/gitlabhq!3385
-
GitLab Release Tools Bot authored
Improper access control allows the attacker to comment in internal commit after they are no longer admin See merge request gitlab/gitlabhq!3392
-
Charlie Ablett authored
Improper access control allows the attacker to comment in internal commit after they are no longer admin
-
GitLab Release Tools Bot authored
Merge branch 'security-2914-labels-visible-despite-no-access-to-issues-repositories-12-2' into '12-2-stable' Labels visible despite no access to issues & repositories See merge request gitlab/gitlabhq!3431
-
GitLab Release Tools Bot authored
Project path reveals labels from Private project if the issue is moved to public project See merge request gitlab/gitlabhq!3445
-
GitLab Release Tools Bot authored
Merge branch 'security-ag-hide-private-members-in-project-member-autocomplete-12-2' into '12-2-stable' Hide private members in project member autocomplete See merge request gitlab/gitlabhq!3448
-
GitLab Release Tools Bot authored
Private/internal repository enumeration via bruteforce on a vulnerable URL See merge request gitlab/gitlabhq!3456
-
GitLab Release Tools Bot authored
Mask sentry auth token See merge request gitlab/gitlabhq!3464
-
GitLab Release Tools Bot authored
Sanitize search text to prevent XSS See merge request gitlab/gitlabhq!3470
-
GitLab Release Tools Bot authored
Require Maintainer permission on group where project is transferred to See merge request gitlab/gitlabhq!3473
-
GitLab Release Tools Bot authored
Use the '\A' and '\z' regex anchors in `InternalRedirect` to mitigate an Open Redirect issue. See merge request gitlab/gitlabhq!3476
-
GitLab Release Tools Bot authored
Pass all wiki markup formats through our Banzai pipeline filters See merge request gitlab/gitlabhq!3479
-
GitLab Release Tools Bot authored
Handle Stored XSS for Grafana URL in settings See merge request gitlab/gitlabhq!3481
-
David Wilkins authored
- Extend Gitlab::UrlBlocker to allow relative urls (require_absolute setting). The new `require_absolute` setting defaults to true, which is the existing behavior. - Extend AddressableUrlValidator to accept `require_abosolute` and default to the existing behavior - Add validation for ApplicationSetting#grafana_url to validate that the URL does not contain XSS but can be a valid relative or absolute url. - In the case of existing stored URLs, validate the stored URL does not contain XSS. If the stored URL contains stored XSS or is an otherwise invalid URL, return the default database column value. - Add tests for Gitlab::UrlBlocker to test require_absolute setting - Add tests for AddressableUrlValidator - Add tests for ApplicationSetting#grafana_url
-
GitLab Release Tools Bot authored
Filter out search results based on permissions to avoid bugs leaking data See merge request gitlab/gitlabhq!3494
-
Bob Van Landuyt authored
When a user updates a merge request coming from a fork, they should not be able to set `force_remove_source_branch` if they cannot push code to the source project. Otherwise developers of the target project could remove the source branch of the source project by setting this flag through the API.
-
- Oct 23, 2019
-
-
Charlie Ablett authored
-