CVE-2022-4331
First published: Thu Mar 09 2023(Updated: )
An issue has been discovered in GitLab EE affecting all versions starting from 15.1 before 15.7.8, all versions starting from 15.8 before 15.8.4, all versions starting from 15.9 before 15.9.2. If a group with SAML SSO enabled is transferred to a new namespace as a child group, it's possible previously removed malicious maintainer or owner of the child group can still gain access to the group via SSO or a SCIM token to perform actions on the group.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=15.1<15.7.8 | |
| GitLab | >=15.8<15.8.4 | |
| GitLab | >=15.9<15.9.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-4331?
CVE-2022-4331 has been assigned a moderate severity level due to its potential impact on SAML SSO configurations.
How do I fix CVE-2022-4331?
To address CVE-2022-4331, upgrade GitLab to version 15.7.8, 15.8.4, or 15.9.2 or later.
Which versions of GitLab are affected by CVE-2022-4331?
CVE-2022-4331 affects GitLab versions from 15.1 to 15.7.8, from 15.8 to 15.8.4, and from 15.9 to 15.9.2.
What type of issue is described in CVE-2022-4331?
CVE-2022-4331 describes a vulnerability related to group transfer with SAML SSO enabled in GitLab.
What happens if I do not address CVE-2022-4331?
If CVE-2022-4331 is not addressed, it could potentially lead to unauthorized access due to misconfigured SAML SSO settings.
- agent/type
- agent/references
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/15.1
- version/gitlab/15.8
- version/gitlab/15.9