- Jul 01, 2020
-
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
- Jun 29, 2020
-
-
GitLab Release Tools Bot authored
Do not show activity for users with private profiles See merge request gitlab-org/security/gitlab!689
-
GitLab Release Tools Bot authored
Check access when sending TODOs related to merge requests See merge request gitlab-org/security/gitlab!674
-
GitLab Release Tools Bot authored
Disable caching for wiki attachments See merge request gitlab-org/security/gitlab!660
-
GitLab Release Tools Bot authored
Fix null byte error in upload path See merge request gitlab-org/security/gitlab!574
-
GitLab Release Tools Bot authored
Resolve "Cross-Site Scripting In BitbucketServer Import" See merge request gitlab-org/security/gitlab!259
-
GitLab Release Tools Bot authored
Fix note author name rendering See merge request gitlab-org/security/gitlab!661
-
GitLab Release Tools Bot authored
Fixed group deploy token API authorizations See merge request gitlab-org/security/gitlab!675
-
GitLab Release Tools Bot authored
Change from hybrid to JSON cookies serializer See merge request gitlab-org/security/gitlab!693
-
JSON has been the default serializer since Rails 4.1. Hybrid serializer was meant to allow backward compatibility when upgrading pre-Rails 4.1. It's been some time since we upgraded to Rails 4.1 so now we don't need the hybrid serializer anymore. This also causes security concerns since the previous serializer was Marshal.
-
GitLab Release Tools Bot authored
Stored XSS on the Error Tracking page See merge request gitlab-org/security/gitlab!627
-
GitLab Release Tools Bot authored
Upgrade swagger-ui to solve XSS issues See merge request gitlab-org/security/gitlab!637
-
GitLab Release Tools Bot authored
Validate group names with Rails HTML sanitizer See merge request gitlab-org/security/gitlab!631
-
GitLab Release Tools Bot authored
Fix XSS in Banzai's `#data_attributes_for` See merge request gitlab-org/security/gitlab!603
-
GitLab Release Tools Bot authored
Update permissions for time tracking endpoints See merge request gitlab-org/security/gitlab!620
-
GitLab Release Tools Bot authored
Update Kaminari gem See merge request gitlab-org/security/gitlab!671
-
GitLab Release Tools Bot authored
Make sure user info is sanitized when rendered See merge request gitlab-org/security/gitlab!596
-
-
GitLab Release Tools Bot authored
Merge branch 'security-fix_project_authorizations_for_security_dashboard-12-10' into '12-10-stable-ee' Security fix project authorizations for security dashboard See merge request gitlab-org/security/gitlab!584
-
-
GitLab Release Tools Bot authored
Fixes pypi XSS See merge request gitlab-org/security/gitlab!558
-
Showing events is a mistake when the user has a private profile
-
- Jun 24, 2020
-
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
-
Mayra Cabrera authored
Document correct registry port to test SSL See merge request gitlab-org/gitlab!35043
-
This commit backports 9079f503
-
Mayra Cabrera authored
Correctly count wiki pages in sidebar See merge request gitlab-org/gitlab!34174
- Jun 23, 2020
-
-
Mario de la Ossa authored
We were allowing users to store XSS in `#data_attributes_for` by not dealing with HTML Entities. We now escape HTML entities out, thus fixing the problem.
-
Nick Thomas authored
-
- Jun 22, 2020
-
-
Etienne Baqué authored
Updated authorizations for group deploy tokens API. Updated rspec accordingly.
-
Dominic Couture authored
-
Dheeraj Joshi authored
-
Markus Koller authored
These were served with `Content-Disposition: inline` in some situations, which led to a Stored XSS attack using SVG files. Workhorse has protections specifically against SVG files and will rewrite the `Content-Disposition` header to `attachment`, but this processing is skipped for cached 304 responses. By disabling caching we force Workhorse to always rewrite this header.
-
Vijay Hawoldar authored
-
- Jun 18, 2020
-
-
GitLab currently uses a regex to validate group names. It has proved difficult to prevent XSS problems. In trying to chase XSS issues we've tightened the regex and don't allow some completely benign characters on their own, such as parentheses. This results in a worse user experience and may not really protect from XSS. Instead, this now uses the Rails::Html::FullSanitizer to validate group names.
-