Vulnerability Description
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. OAuth, LDAP, SAML) in GitLab CE/EE versions 14.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allowing attackers to potentially take over accounts
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Gitlab | Gitlab | >= 14.7.0, < 14.7.7 |
Related Weaknesses (CWE)
References
- http://packetstormsecurity.com/files/166828/Gitlab-14.9-Authentication-Bypass.htThird Party AdvisoryVDB Entry
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1162.jsonVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/issues/357210Broken Link
- http://packetstormsecurity.com/files/166828/Gitlab-14.9-Authentication-Bypass.htThird Party AdvisoryVDB Entry
- https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1162.jsonVendor Advisory
- https://gitlab.com/gitlab-org/gitlab/-/issues/357210Broken Link
FAQ
What is CVE-2022-1162?
CVE-2022-1162 is a vulnerability with a CVSS score of 9.1 (CRITICAL). A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. OAuth, LDAP, SAML) in GitLab CE/EE versions 14.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 a...
How severe is CVE-2022-1162?
CVE-2022-1162 has been rated CRITICAL with a CVSS base score of 9.1/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2022-1162?
Check the references section above for vendor advisories and patch information. Affected products include: Gitlab Gitlab.