dbcve.org
GitLabApplication

CVE-2022-0123

MEDIUM · 6.8 CVSS v3.1 Published 2022-03-28
Fix available
A fix is available. Upgrade to 14.4.5 / 14.5.3 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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 affecting GitLab versions prior to 14.4.5, between 14.5.0 and 14.5.3, and between 14.6.0 and 14.6.1. GitLab does not validate SSL certificates for some of external CI services which makes it possible to perform MitM attacks on connections to these external services.

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 versions prior to 14.4.5, between 14.5.0-14.5.3, and between 14.6.0-14.6.1 fail to validate SSL certificates when connecting to certain external CI services, allowing attackers on the network path to intercept and potentially modify traffic via Man-in-the-Middle attacks.

MitigationUpgrade GitLab to version 14.4.5, 14.5.3, 14.6.1 or later. For self-managed instances, plan a maintenance window and ensure backups before performing the upgrade.

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:< 14.4.5>= 14.5.0, < 14.5.3>= 14.6.0, < 14.6.1

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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. Identify GitLab deployment type
    Confirm whether this is a self-managed GitLab instance. For GitLab SaaS (gitlab.com), the vulnerability is patched by GitLab. Only self-managed installations allow version inspection.
    Affected if Instance is self-managed and running an affected version below 14.4.5, between 14.5.0-14.5.3, or between 14.6.0-14.6.1
  2. Determine installed GitLab version
    Run command: sudo gitlab-rake gitlab:env:info or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file. Alternatively, visit Admin Area > Settings > General and view the GitLab version displayed.
    Affected if Installed version is prior to 14.4.5, between 14.5.0-14.5.3 inclusive, or between 14.6.0-14.6.1 inclusive
  3. Verify external CI service configuration
    Navigate to Admin Area > CI/CD > Runners or project Settings > CI/CD > Runners. Check if external/third-party CI runners are configured, particularly runners that connect to external services outside your network.
    Affected if External or third-party CI runners are registered and used for pipeline execution
  4. Inspect SSL verification settings for CI jobs
    Check CI/CD variables for CI_DISABLE_SSL_VERIFICATION or similar variables. Review .gitlab-ci.yml files for any jobs that disable certificate verification via environment variables.
    Affected if SSL verification is explicitly disabled via CI variables, or runners are configured to skip SSL verification

A self-managed GitLab instance is affected if it runs version 14.4.4 or earlier, 14.5.0-14.5.3, or 14.6.0-14.6.1 AND has external CI runners configured that could receive unvalidated SSL connections.

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.4.5 / 14.5.3 / 14.6.1 or later
Fixed in 14.4.514.5.314.6.1
Interim mitigation

Upgrade GitLab to version 14.4.5, 14.5.3, 14.6.1 or later. For self-managed instances, plan a maintenance window and ensure backups before performing the upgrade.

Recommended fix High confidence

14.6.1 or later

  1. 1. Back up your GitLab instance data and configuration
  2. 2. Review the GitLab upgrade documentation for your installation method (Omnibus, source, etc.)
  3. 3. For GitLab installations, upgrade to version 14.6.1 or later using your package manager or source installation method
  4. 4. After upgrade, verify that SSL certificate validation is working correctly for external CI service connections
  5. 5. Test CI/CD pipelines that connect to external services to ensure proper certificate validation is occurring
Caveat GitLab upgrades may include database migrations and configuration changes; review release notes for any breaking changes between your current version and 14.6.1

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-0123 — 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-0123 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