- Apr 27, 2021
-
-
GitLab Release Tools Bot authored
[merge-train skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
Henri Philipps authored
Update mermaid to version 8.9.2 See merge request gitlab-org/security/gitlab!1363
-
GitLab Release Tools Bot authored
Do not expose pull mirror username and password See merge request gitlab-org/security/gitlab!1355
-
GitLab Release Tools Bot authored
Merge branch 'security-disallow-changing-timestamps-on-issue-create-update-13-10' into '13-10-stable-ee' Prevent non-owners to set system_note_timestamp See merge request gitlab-org/security/gitlab!1359
-
GitLab Release Tools Bot authored
Merge branch 'security-322500-disable-gitaly-branch-pagination-ff-by-default-13-10' into '13-10-stable-ee' Disable keyset pagination for branches by default See merge request gitlab-org/security/gitlab!1367
-
GitLab Release Tools Bot authored
Restrict the dependency proxy auth service See merge request gitlab-org/security/gitlab!1370
-
GitLab Release Tools Bot authored
Bump Carrierwave gem to v1.3.2 See merge request gitlab-org/security/gitlab!1350
-
GitLab Release Tools Bot authored
Merge branch 'security-327155-prevent-mutation-execution-with-read-api-tokens-13-10' into '13-10-stable-ee' Prevent mutation execution with read api tokens See merge request gitlab-org/security/gitlab!1343
-
- Apr 26, 2021
-
-
David Fernandez authored
Any objects other than `User` (such as `DeployToken`) are not allowed Changelog: security
-
- Apr 23, 2021
-
-
Nick Thomas authored
It seems that with this feature flag enabled, pagination doesn't work correctly in conjunction with a search. The FF is already disabled on GitLab.com, but disabling it in the YAML file means that self-managed instances will also be protected from the security issue (unless they explicitly opt-in to some beta code, of course). Changelog: security
-
Dominic Couture authored
-
- Apr 22, 2021
-
-
Alexandru Croitor authored
When an issue is created or updated though API for import purposes we allow providing created_at and updated_at params these would then be reflected also in system notes. Only admins and project owners should be able to set these dates.
-
- Apr 20, 2021
-
-
Vasilli Iakliushin authored
Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/230864 * Remove password value from the pull mirror form * Hide username from mirror url
-
- Apr 14, 2021
-
-
GitLab Release Tools Bot authored
-
Mike Kozono authored
-
- Apr 13, 2021
-
-
GitLab Release Tools Bot authored
[merge-train skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
Robert Speicher authored
Check content type before running exiftool See merge request gitlab-org/security/gitlab!1341
-
Robert Speicher authored
Security ruby saml auth bypass fix See merge request gitlab-org/security/gitlab!1332
-
Robert Speicher authored
Detect file format before checking exif headers See merge request gitlab-org/security/gitlab!1338
-
- Apr 12, 2021
-
-
Alexis Kalderimis authored
Verify that read_api tokens cannot run mutations. Also: adds tests use of OAuth tokens for GraphQL We make some changes to the sessionless_authentication module in order to capture the request_authenticator, so that we can access the token scopes, without making any extra queries. We ensure we always authorize the mutation, which, like all resolvers, needs to opt in to the check. Unlike resolvers, mutations should always raise. So `BaseMutation.authorized?` raises on failure. Logic for handling scopes is pushed down to the `ObjectAuthorization` class, and encapsulated in the `ScopeValidator`, which limits the methods that can be called by resolvers.
-
- Apr 11, 2021
-
-
Jan Provaznik authored
Assures that exiftool runs for jpeg/tiff images only.
-
- Apr 09, 2021
-
-
Before running exiftool from rake task, file's MIME type is checked.
-
- Apr 08, 2021
-
-
-
Vladimir Shushlin authored
By default dora4 metrics controller returns data for last 3 months We use 2021-01-01 as fixture date in specs. So controllers stoped returning this data on 2021-04-02 Also, max range was calculated as 91 days, while it's actually possible to have 92 days in 3 months. I caught this trying to fix the issue (cherry picked from commit b76bd0d8)
-
- Apr 01, 2021
-
-
GitLab Release Tools Bot authored
[merge-train skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
Robert Speicher authored
Prepare 13.10.2-ee release See merge request gitlab-org/gitlab!58151
-
- Mar 31, 2021
-