CVE-2022-4331
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…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.74%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.1
- 7.3 HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
- EPSS
- 0.74% probability · 53th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-284
- Affected
- gitlab/gitlab
- Source
- cve@gitlab.com
References
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-4331.jsonVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/issues/385050Broken Link
- https://hackerone.com/reports/1791518Permissions Required
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-4331.jsonVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/issues/385050Broken Link
- https://hackerone.com/reports/1791518Permissions Required
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.