==================================================================== CERT-Renater Note d'Information No. 2021/VULN062 _____________________________________________________________________ DATE : 02/02/2021 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running GitLab versions prior to 13.8.2, 13.7.6, 13.6.6. ===================================================================== https://about.gitlab.com/blog/2021/02/01/security-release-gitlab-13-8-2-released/ _____________________________________________________________________ GitLab Security Release: 13.8.2, 13.7.6 and 13.6.6 Learn more about GitLab Security Release: 13.8.2, 13.7.6 and 13.6.6 for GitLab Community Edition (CE) and Enterprise Edition (EE) Today we are releasing versions 13.8.2, 13.7.6 and 13.6.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab releases patches for vulnerabilities in dedicated security releases. There are two types of security releases: a monthly, scheduled security release, released a week after the feature release (which deploys on the 22nd of each month), and ad-hoc security releases for critical vulnerabilities. For more information, you can visit our security FAQ. You can see all of our regular and security release blog posts here. In addition, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is highly recommended that all customers upgrade to the latest security release for their supported version. You can read more best practices in securing your GitLab instance in our blog post. Security release issue: https://gitlab.com/gitlab-org/gitlab/-/issues/296889 Stored XSS in merge request An issue has been discovered in GitLab affecting all versions starting with 13.7. GitLab was vulnerable to a stored XSS in merge requests. We have requested a CVE ID and will update this blog post when it is assigned. Thanks ashish_r_padelkar for reporting this vulnerability through our HackerOne bug bounty program. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Stored XSS in epic's pages An issue has been discovered in GitLab affecting all versions starting with 11.8. GitLab was vulnerable to a stored XSS in the epics page, which could be exploited with user interactions. We have requested a CVE ID and will update this blog post when it is assigned. Thanks mike12 for reporting this vulnerability through our HackerOne bug bounty program. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Sensitive GraphQL variables exposed in structured log An information disclosure issue in GitLab 12.0+ allowed a user with access to the server logs to see sensitive information that wasn't properly redacted. This is a medium severity issue (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 6.2). We have requested a CVE ID and will update this blog post when it is assigned. This vulnerability has been discovered internally by the GitLab team. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Guest user can see tag names in private projects Improper authorization in GitLab 12.8+ allows a guest user in a private project to view tag data that should be inaccessible on the releases page. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, 4.3). It is now mitigated in the latest release and is assigned CVE-2021-22172. Thanks @izzsec for reporting this vulnerability through our HackerOne bug bounty program. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Information disclosure via error message An issue was identified in GitLab EE 13.4 or later which could disclose internal IP address via error messages. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, 4.3). It is now mitigated in the latest release and is assigned CVE-2021-22169. This vulnerability has been discovered internally by the GitLab team. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. DNS rebinding protection bypass An issue has been discovered in GitLab affecting all versions starting with 12.2. GitLab was vulnerable to a DNS rebinding protection bypass. We have requested a CVE ID and will update this blog post when it is assigned. Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Validate existence of private project An issue has been discovered in GitLab affecting all versions. Validate the use of a specific name for private project in a group was posible. We have requested a CVE ID and will update this blog post when it is assigned. Thanks milindpurswani for reporting this vulnerability through our HackerOne bug bounty program. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Updating To update GitLab, see the Update page. To update Gitlab Runner, see the Updating the Runner page. Receive Security Release Notifications To receive security release blog notifications delivered to your inbox, visit our contact us page. To receive security release blog notifications via RSS, subscribe to our RSS feed. ========================================================= + CERT-RENATER | tel : 01-53-94-20-44 + + 23/25 Rue Daviel | fax : 01-53-94-20-41 + + 75013 Paris | email:cert@support.renater.fr + =========================================================