dbcve.org
GitLabApplication

CVE-2022-3793

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-10
Fix available
A fix is available. Upgrade to 15.3.5 / 15.4.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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 improper authorization issue in GitLab CE/EE affecting all versions from 14.4 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows an attacker to read variables set directly in a GitLab CI/CD configuration file they don't have access to.

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

An improper authorization vulnerability in GitLab CE/EE allows authenticated users to read CI/CD configuration variables from projects or pipelines they don't have access to, resulting in information disclosure.

MitigationUpgrade GitLab to version 15.3.5, 15.4.4, 15.5.2 or later to patch the authorization bypass.

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:>= 12.6.0, < 15.3.5>= 15.4.0, < 15.4.4>= 15.5.0, < 15.5.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Determine installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the Admin Area > Overview > System Info page in the web UI to find the exact version number
    Affected if The version falls within >= 12.6.0 and < 15.3.5, OR >= 15.4.0 and < 15.4.4, OR >= 15.5.0 and < 15.5.2
  2. Verify CI/CD pipeline functionality is enabled
    Check if CI/CD is enabled in Admin Area > Settings > CI/CD > General pipelines, or look for pipelines in any project
    Affected if CI/CD pipelines are active and the GitLab version is in the affected range
  3. Confirm multi-project or shared pipeline access exists
    Review which authenticated users have access to different projects via Project > Settings > Members, and check if any pipelines reference other projects through `project:` keyword in .gitlab-ci.yml
    Affected if Multiple projects exist with CI/CD pipelines and users have varying access levels across those projects

The environment is affected if the installed GitLab version is within the vulnerable ranges AND CI/CD pipelines with variables are in use with users having different access levels across projects.

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 15.3.5 / 15.4.4 / 15.5.2 or later
Fixed in 15.3.515.4.415.5.2
Interim mitigation

Upgrade GitLab to version 15.3.5, 15.4.4, 15.5.2 or later to patch the authorization bypass.

Recommended fix High confidence

15.5.2 (or later in the 15.x stable series)

  1. 1. Back up your GitLab instance before starting the upgrade
  2. 2. For Omnibus installations: Run 'sudo apt-get update' and 'sudo apt-get install gitlab-ce' (or 'gitlab-ee') to upgrade to the latest patch in your current version stream, or specify the version: 'sudo apt-get install gitlab-ce=15.5.2'
  3. 3. For source installations: Stop GitLab, download the 15.5.2 release from gitlab.com, replace the source files, then run bundle install and rake gitlab:env:info RAILS_ENV=production
  4. 4. Run 'sudo gitlab-ctl reconfigure' after the package installation completes
  5. 5. Verify the upgrade by running 'sudo gitlab-rake gitlab:env:info' and confirm the version is 15.5.2 or later
Caveat GitLab upgrades within the same major version typically have minimal breaking changes, but always review release notes before upgrading and test in a staging environment first

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3793 — 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-3793 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