dbcve.org
GitLabApplication

CVE-2022-0738

HIGH · 7.5 CVSS v3.1 Published 2022-03-28
Fix available
A fix is available. Upgrade to 14.6.5 / 14.7.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue has been discovered in GitLab affecting all versions starting from 14.6 before 14.6.5, all versions starting from 14.7 before 14.7.4, all versions starting from 14.8 before 14.8.2. GitLab was leaking user passwords when adding mirrors with SSH credentials under specific conditions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab had an information disclosure vulnerability where user passwords were inadvertently leaked when configuring repository mirrors with SSH credentials. The password exposure occurred under specific conditions related to the mirror configuration workflow, likely in logs or API responses.

MitigationUpdate GitLab to version 14.6.5, 14.7.4, 14.8.2 or later. Review access logs and audit logs for any evidence of exposed credentials and rotate any potentially compromised passwords.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 10.0, < 14.6.5>= 14.7, < 14.7.4>= 14.8, < 14.8.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` to determine the exact installed version. Alternatively, visit the GitLab admin area Help page which displays the version number.
    Affected if The version falls within these ranges: >= 10.0 and < 14.6.5, OR >= 14.7 and < 14.7.4, OR >= 14.8 and < 14.8.2
  2. Determine if repository mirrors were configured
    Check if any repository mirror configurations exist by navigating to Project Settings > Repository > Mirrored repositories, or query the database table `project_mirror_data` if database access is available.
    Affected if Mirror configurations with SSH credentials were created or modified in the affected version
  3. Review application logs for password exposure
    Search GitLab production logs (typically in `/var/log/gitlab/gitlab-rails/production.log`) for entries containing terms like 'mirror', 'password', 'ssh_password', or credential values. Use grep or log analysis tools to search for patterns where passwords may have been logged.
    Affected if Log entries contain plaintext passwords from mirror configuration submissions
  4. Review API audit logs
    Check GitLab audit logs (in the UI: Admin Area > Monitoring > Logs > Audit Events, or database table `audit_events`) for any API calls to the mirror configuration endpoint that may have exposed credentials in request payloads.
    Affected if Audit logs show API requests with password parameters visible in plain text

You are affected if your GitLab version is within the affected ranges AND repository mirrors with SSH credentials were configured, as the password would have been logged or exposed in API responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.6.5 / 14.7.4 / 14.8.2 or later
Fixed in 14.6.514.7.414.8.2
Interim mitigation

Update GitLab to version 14.6.5, 14.7.4, 14.8.2 or later. Review access logs and audit logs for any evidence of exposed credentials and rotate any potentially compromised passwords.

Recommended fix High confidence

14.8.2 (or latest 14.x stable release)

  1. 1. Create a full backup of the GitLab instance before upgrading
  2. 2. Review the current GitLab version (gitLab-rake gitlab:env:info) to determine which upgrade path is needed
  3. 3. For versions 14.0-14.6.x: Upgrade to 14.6.5 or later (preferably to 14.8.2 or latest 14.x stable
  4. 4. For versions 14.7.x: Upgrade to 14.7.4 or later (preferably to 14.8.2 or latest 14.x stable
  5. 5. For versions 14.8.x: Upgrade to 14.8.2 or later (preferably latest 14.x stable
  6. 6. After upgrade, verify the installation (gitlab-rake gitlab:check)
  7. 7. As a security precaution, review and rotate any SSH credentials that were entered in mirror repository settings, as they may have been exposed
Caveat Minor version upgrades in GitLab typically do not introduce breaking changes; however, always review the release notes for any configuration or API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0738 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data