Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2022-1680

9.9 · CRITICAL
Published Jun 6, 2022 gitlab EPSS 15.90% (97th pctl)

Overview

CVE-2022-1680 is a critical-severity vulnerability affecting gitlab gitlab. It was published on June 6, 2022 and has a CVSS 3.1 base score of 9.9 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.9, rated CRITICAL. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical Description

An account takeover issue has been discovered in GitLab EE affecting all versions starting from 11.10 before 14.9.5, all versions starting from 14.10 before 14.10.4, all versions starting from 15.0 before 15.0.1. When group SAML SSO is configured, the SCIM feature (available only on Premium+ subscriptions) may allow any owner of a Premium group to invite arbitrary users through their username and email, then change those users' email addresses via SCIM to an attacker controlled email address and thus - in the absence of 2FA - take over those accounts. It is also possible for the attacker to change the display name and username of the targeted account.

Remediation

Check the references section for vendor advisories and patches from gitlab. Update gitlab to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
gitlab gitlab >= 11.10.0, < 14.9.5 Affected

Frequently Asked Questions

What is CVE-2022-1680?

CVE-2022-1680 is a critical-severity vulnerability affecting gitlab gitlab. It was published on June 6, 2022 and has a CVSS 3.1 base score of 9.9 (CRITICAL).

How severe is CVE-2022-1680?

This vulnerability has a CVSS 3.1 base score of 9.9, rated CRITICAL. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-1680?

Check the references section for vendor advisories and patches from gitlab. Update gitlab to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-1680?

CyberStrike's AI-powered security agents can automatically detect CVE-2022-1680 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.