SB2022120119 - Multiple vulnerabilities in GitLab Community Edition (CE) and Enterprise Edition (EE)



SB2022120119 - Multiple vulnerabilities in GitLab Community Edition (CE) and Enterprise Edition (EE)

Published: December 1, 2022

Security Bulletin ID SB2022120119
Severity
Medium
Patch available
YES
Number of vulnerabilities 4
Exploitation vector Remote access
Highest impact Data manipulation

Breakdown by Severity

Medium 25% Low 75%
  • Low
  • Medium
  • High
  • Critical

Description

This security bulletin contains information about 4 secuirty vulnerabilities.


1) Improper Authentication (CVE-ID: CVE-2022-3820)

The vulnerability allows a remote user to bypass authentication process.

The vulnerability exists due to an error in when processing authentication requests with some Package Registries when IP address restrictions were configured. A remote administrator can misuse it from any location.


2) Improper Authorization (CVE-ID: CVE-2022-3740)

The vulnerability allows a remote user to bypass authentication process.

The vulnerability exists due to improper authorization within the External Authorization service. A remote administrator can access git repositories and package registries by using Deploy tokens or Deploy keys.


3) Cross-site scripting (CVE-ID: CVE-2022-3572)

The disclosed vulnerability allows a remote attacker to perform cross-site scripting (XSS) attacks.

The vulnerability exists due to insufficient sanitization of user-supplied data in Jira Integration. A remote user can trick the victim to follow a specially crafted link and execute arbitrary HTML and script code in user's browser in context of vulnerable website.

Successful exploitation of this vulnerability may allow a remote attacker to steal potentially sensitive information, change appearance of the web page, perform phishing and drive-by-download attacks.


4) Improper access control (CVE-ID: CVE-2022-3482)

The vulnerability allows a remote attacker to gain unauthorized access to otherwise restricted functionality.

The vulnerability exists due to improper access restrictions. A remote attacker can see release names even when releases were set to be restricted to project members only.


Remediation

Install update from vendor's website.