Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 =========================================================================== AUSCERT External Security Bulletin Redistribution ESB-2021.2299 GitLab Security Release 14.0.2, 13.12.6, and 13.11.6 2 July 2021 =========================================================================== AusCERT Security Bulletin Summary --------------------------------- Product: GitLab Community Edition GitLab Enterprise Edition Publisher: GitLab Operating System: Windows UNIX variants (UNIX, Linux, OSX) Virtualisation Impact/Access: Cross-site Request Forgery -- Remote with User Interaction Cross-site Scripting -- Remote with User Interaction Denial of Service -- Existing Account Provide Misleading Information -- Remote with User Interaction Access Confidential Data -- Remote/Unauthenticated Unauthorised Access -- Existing Account Reduced Security -- Existing Account Resolution: Patch/Upgrade CVE Names: CVE-2021-22223 Original Bulletin: https://about.gitlab.com/releases/2021/07/01/security-release-gitlab-14-0-2-released/ - --------------------------BEGIN INCLUDED TEXT-------------------- Jul 1, 2021 - Costel Maxim GitLab Security Release: 14.0.2, 13.12.6, and 13.11.6 Learn more about GitLab Security Release: 14.0.2, 13.12.6, and 13.11.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). Today we are releasing versions 14.0.2, 13.12.6, and 13.11.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. Table of Fixes Title Severity DoS using Webhook connections high CSRF on GraphQL API allows executing mutations through GET requests high Private projects information disclosure medium Denial of service of user profile page medium Single sign-on users not getting blocked medium Some users can push to Protected Branch with Deploy keys medium A deactivated user can access data through GraphQL medium Reflected XSS in release edit page medium Clipboard DOM-based XSS medium Stored XSS on Audit Log medium Forks of public projects by project members could leak codebase medium Improper text rendering medium HTML Injection in full name field low Update Nokogiri low Update Mattermost medium Update Redis medium Update Rdoc medium Update libxml2 medium Update Rails gem medium DoS using Webhook connections A vulnerability was discovered in GitLab versions before 14.0.2, 13.12.6, 13.11.6. GitLab Webhook feature could be abused to perform denial of service attacks. This is a high severity issue (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/ I:N/A:H, 7.7). We have requested a CVE ID and will update this blog post when it is assigned. Thanks afewgoats 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. CSRF on GraphQL API allows executing mutations through GET requests A cross-site request forgery vulnerability in the GraphQL API in GitLab since version 13.12 and before versions 13.12.6 and 14.0.2 allowed an attacker to call mutations as the victim. This is a high severity issue (CVSS:3.0/AV:N/AC:L /PR:N/UI:R/S:U/C:L/I:H/A:N, 7.1). We have requested a CVE ID and will update this blog post when it is assigned. Thanks 0xn3va 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. Private projects information disclosure An information disclosure vulnerability was found in GitLab EE versions 13.10 and later allowed a user to read project details. This is a medium severity issue (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, 4.3). We have requested a CVE ID and will update this blog post when it is assigned. Thanks 0xn3va 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. Denial of service of user profile page A denial of service in user's profile page is found starting with GitLab CE/EE 8.0 that allows attacker to reject access to their profile page via using a specially crafted username. This is a medium severity issue (CVSS:3.0/AV:N/AC:L /PR:L/UI:N/S:U/C:N/I:N/A:L, 4.3). We have requested a CVE ID and will update this blog post when it is assigned. Thanks maruthi12 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. Single sign-on users not getting blocked Improper access control in GitLab EE before versions 13.11.6, 13.12.6, and 14.0.2 allowed users to be created via single sign on despite user cap being enabled. This is a medium severity issue (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/ I:L/A:N, 4.2). We have requested a CVE ID and will update this blog post when it is assigned. Thanks bingomzan 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. Some users can push to Protected Branch with Deploy keys Under certain conditions, some users were able to push to protected branches that were restricted to deploy keys in GitLab CE/EE since version 13.9. This is a medium severity issue (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N, 6.5). 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. A deactivated user can access data through GraphQL An issue has been discovered in GitLab affecting all versions. Improper access control allows unauthorised users to access project details using Graphql. This is a medium severity issue (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, 6.5). We have requested a CVE ID and will update this blog post when it is assigned. Thanks joaxcar 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. Reflected XSS in release edit page A reflected cross-site scripting vulnerability in GitLab before versions 13.11.6, 13.12.6 and 14.0.2 allowed an attacker to send a malicious link to a victim and trigger actions on their behalf if they clicked it. This is a medium severity issue (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, 6.1). 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. Clipboard DOM-based XSS Improper input sanitization in markdown in GitLab CE/EE version 13.11 and up allowed an attacker to exploit a stored cross-site scripting vulnerability via a specially-crafted input. This is a medium severity issue (CVSS:3.0/AV:N/AC:H/ PR:N/UI:R/S:C/C:L/I:L/A:N, 4.7). We have requested a CVE ID and will update this blog post when it is assigned. Thanks vovohelofor 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 on Audit Log Client-Side code injection through Feature Flag name starting with GitLab CE/EE 11.9 allows a specially crafted feature flag name to PUT requests on behalf of other users via clicking on a link. This is a medium severity issue (CVSS:3.0/ AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, 6.1). It is now mitigated in the latest release and is assigned CVE-2021-22223. 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. Forks of public projects by project members could leak codebase An issue has been discovered in GitLab CE/EE affecting all versions starting with 12.8. Under a special condition it was possible to access data of an internal repository through project fork done by a project member. This is a medium severity issue (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, 5.9). 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. Improper text rendering Improper text rendering while rendering merge requests could be exploited to submit malicious code. This vulnerability affects GitLab CE/EE 9.3 and later through 13.11.6, 13.12.6, and 14.0.2. This is a medium severity issue (CVSS:3.0 /AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N, 4.9). 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. HTML Injection in full name field HTML injection was possible via the full name field before versions 13.11.6, 13.12.6, and 14.0.2 in GitLab CE. This is a high severity issue (CVSS:3.0/AV:N/ AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N, 3.5). We have requested a CVE ID and will update this blog post when it is assigned. Thanks andor404 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. Update Nokogiri Nokogiri has been upgraded to 1.11.4 in order to mitigate security concerns. Versions affected Affects all versions. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Update Mattermost Mattermost has been upgraded to 5.33.5 in order to mitigate security concerns. Versions affected Affects versions 13.10 and later. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Update Redis Redis has been upgraded to 6.0.14 in order to mitigate security concerns. Versions affected Affects versions 13.9 and later. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Update Rdoc Rdoc has been upgraded to 6.3.1 in order to mitigate security concerns. Versions affected Affects all versions. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Update libxml2 libxml2 has been upgraded to 2.9.11 in order to mitigate security concerns. Versions affected Affects all versions. Remediation We strongly recommend that all installations running an affected version above are upgraded to the latest version as soon as possible. Update Rails gem The Rails gem has been upgraded to 6.0.3.7 in order to mitigate security concerns. Versions affected Affects all versions. 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. - --------------------------END INCLUDED TEXT-------------------- You have received this e-mail bulletin as a result of your organisation's registration with AusCERT. The mailing list you are subscribed to is maintained within your organisation, so if you do not wish to continue receiving these bulletins you should contact your local IT manager. If you do not know who that is, please send an email to auscert@auscert.org.au and we will forward your request to the appropriate person. NOTE: Third Party Rights This security bulletin is provided as a service to AusCERT's members. As AusCERT did not write the document quoted above, AusCERT has had no control over its content. The decision to follow or act on information or advice contained in this security bulletin is the responsibility of each user or organisation, and should be considered in accordance with your organisation's site policies and procedures. AusCERT takes no responsibility for consequences which may arise from following or acting on information or advice contained in this security bulletin. NOTE: This is only the original release of the security bulletin. It may not be updated when updates to the original are made. If downloading at a later date, it is recommended that the bulletin is retrieved directly from the author's website to ensure that the information is still current. Contact information for the authors of the original document is included in the Security Bulletin above. If you have any questions or need further information, please contact them directly. Previous advisories and external security bulletins can be retrieved from: https://www.auscert.org.au/bulletins/ =========================================================================== Australian Computer Emergency Response Team The University of Queensland Brisbane Qld 4072 Internet Email: auscert@auscert.org.au Facsimile: (07) 3365 7031 Telephone: (07) 3365 4417 (International: +61 7 3365 4417) AusCERT personnel answer during Queensland business hours which are GMT+10:00 (AEST). On call after hours for member emergencies only. =========================================================================== -----BEGIN PGP SIGNATURE----- Comment: http://www.auscert.org.au/render.html?it=1967 iQIVAwUBYN5Y4eNLKJtyKPYoAQjxxQ/+MblS4JYaHDlJIuYBWy8/IpQRUbASDiGi 9yfnQPAN25mHuHZwBIQG3D01vswASloAlWORE2GUNk8fSWe9JaT4h60Xpwp7eGFq FUnkSJPp+2IgCtlLNhWlVFkjy22+atquC1j75jzmLkKg/g5BxLpTzO5K4RCbJPwa xkVtpWmFlT2gQuNrGdrnnRvv4xBO1ggOoGVXEhdI7xgAdIiIXgHQtsdN0f8XaIul /xDrdZNp5F52Efke8I0QDTFsaklXrhZr7Gdw1YNLA0zsgRMCjR173d8c0d0LMzlE 0UXn0FiaIBc2uhmns+4xD5xfpkP+a791otj8f4/uZa2aUKQ4xR1bBfOEi47z3chE uJwmr5Ldekaz/dOKHsqIJ4ImSR4sNOYz5VSIlZ+LMyfaVY3j8a75nvlp0Y+5vfo/ WljVpnEdsdKIAlCmFtCQSrQU5PqYr2HfGhxo59rGOWRUIstATgRisPtpQ2H6gCpu TSka6neeEprbGvCrRgteOXS3Kl6keSqOLiACol/FK5RpZ/qf05xJKCYfmBaplrRt c0MBtcI5AkFVhjxWJy6EE2eOYfz0PkjrcExAEAn7BekmK3fN/KHBFctVaEISvE6b mNTErAWYqQNKf4C7C8eLHi6ExVXHWq58I9vpsJrZzV6dlO4FNCTB49eMI7tEk8GP nHjevJ7jwCA= =e7oo -----END PGP SIGNATURE-----