CVE-2022-1162
First published: Mon Apr 04 2022(Updated: )
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
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=14.7.0<14.7.7 | |
| GitLab | >=14.7.0<14.7.7 | |
| GitLab | >=14.8.0<14.8.5 | |
| GitLab | >=14.8.0<14.8.5 | |
| GitLab | >=14.9.0<14.9.2 | |
| GitLab | >=14.9.0<14.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-1162?
CVE-2022-1162 is considered a high severity vulnerability due to the potential for account takeover.
How do I fix CVE-2022-1162?
To fix CVE-2022-1162, upgrade your GitLab instance to version 14.7.7, 14.8.5, or 14.9.2 or later.
Which versions of GitLab are affected by CVE-2022-1162?
CVE-2022-1162 affects GitLab CE/EE versions prior to 14.7.7, 14.8.5, and 14.9.2.
What types of accounts are vulnerable in CVE-2022-1162?
CVE-2022-1162 affects accounts registered using OmniAuth providers such as OAuth, LDAP, or SAML.
Can CVE-2022-1162 lead to data breaches?
Yes, due to the hardcoded password issue in CVE-2022-1162, attackers can potentially gain access to user accounts and sensitive data.
- agent/type
- agent/references
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/14.7.0
- version/gitlab/14.8.0
- version/gitlab/14.9.0