# CVE-2022-1162: Hardcoded credentials in GitLab

> Attackers can take over accounts registered via OmniAuth providers due to a hardcoded password in GitLab.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** BIT-gitlab-2022-1162, GHSA-vrqc-vwgr-qqp5, UBUNTU-CVE-2022-1162

## What is CVE-2022-1162?

CVE-2022-1162 is a critical vulnerability in Gitlab Gitlab, published on 4 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-1162?

1 open source package ship an affected version, including gitlab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | From 14.7.0 | 14.7.7, 14.8.5, 14.9.2 |

Products: Gitlab Gitlab.

## How do I fix CVE-2022-1162?

Upgrade gitlab to a fixed version for your release line: 14.7.7, 14.8.5 or 14.9.2.

## Is CVE-2022-1162 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1162 exists.

Public exploit code:

- https://github.com/Greenwolf/CVE-2022-1162 (github_poc): https://github.com/Greenwolf/CVE-2022-1162
- A simple tool to enumerate users in gitlab (github_poc): https://github.com/ipsBruno/CVE-2022-1162
- Gitlab 14.9 - Authentication Bypass (exploitdb)
- GitLab CE/EE - Hard-Coded Credentials (nuclei): http/cves/2022/CVE-2022-1162.yaml

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1162 and fix it if it is affected.

What it is: CVE-2022-1162 is a critical vulnerability in Gitlab Gitlab, published on 4 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1162 exists.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 14.7.0; fixed in 14.7.7, 14.8.5, 14.9.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1162/ (Markdown: https://insights.sbomify.com/CVE-2022-1162/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1162
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1162
- OSV: https://osv.dev/vulnerability/CVE-2022-1162

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1162/
Summaries are generated and may contain mistakes; the official description above is the record.