dbcve.org
GitLabApplication

CVE-2023-1178

MEDIUM · 5.7 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 15.9.6 / 15.10.5 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 CE/EE affecting all versions from 8.6 before 15.9.6, all versions starting from 15.10 before 15.10.5, all versions starting from 15.11 before 15.11.1. File integrity may be compromised when source code or installation packages are pulled from a tag or from a release containing a ref to another commit.

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 · moderate confidence

GitLab CE/EE does not properly verify file integrity when source code or installation packages are pulled from tags or releases that contain a reference to another commit. This allows an attacker to potentially serve different content than intended, compromising the integrity of downloaded artifacts.

MitigationUpgrade GitLab to version 15.9.6, 15.10.5, or 15.11.1 or later to resolve the file integrity verification issue.

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:>= 8.6.0, < 15.9.6>= 15.10, < 15.10.5>= 15.11, < 15.11.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
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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. Check installed GitLab version
    Run command: gitlab-rake gitlab:env:info or check /opt/gitlab/version-manifest.txt, or look at the GitLab admin dashboard under Help > Version
    Affected if Version is 8.6.0 or higher but below 15.9.6, OR between 15.10.0-15.10.5, OR between 15.11.0-15.11.1
  2. Confirm GitLab is pulling from tags or releases
    Review if projects or CI/CD pipelines use git tags, releases, or pull package artifacts from GitLab repositories - this is core GitLab functionality used in most deployments
    Affected if GitLab instance uses tags, releases, or package registry features to distribute code or artifacts
  3. Verify file integrity verification status
    Check GitLab configuration file /etc/gitlab/gitlab.rb for any custom file integrity settings, or review admin area Settings > Repository > Repository settings for tag verification options
    Affected if Default settings are in place (no custom integrity verification overrides) and version is in affected range

User is affected if GitLab version falls within the vulnerable ranges (8.6.0 to 15.9.5, 15.10.0 to 15.10.4, or 15.11.0) AND the instance uses tags, releases, or package registry to distribute code or artifacts.

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.9.6 / 15.10.5 / 15.11.1 or later
Fixed in 15.9.615.10.515.11.1
Interim mitigation

Upgrade GitLab to version 15.9.6, 15.10.5, or 15.11.1 or later to resolve the file integrity verification issue.

Recommended fix High confidence

15.9.6, 15.10.5, or 15.11.1 (or later stable release) depending on your current major version branch

  1. Identify your current GitLab version using `gitlab-rake gitlab:env:info` or the GitLab admin area
  2. Review the GitLab upgrade documentation for your specific version path at https://docs.gitlab.com/ee/update/
  3. Create a full backup of your GitLab instance using `gitlab-backup create`
  4. Ensure you have adequate downtime window as GitLab will be restarted during upgrade
  5. For versions 8.6.0 to 15.9.x: upgrade to version 15.9.6 or later
  6. For versions 15.10.x: upgrade to version 15.10.5 or later
  7. For versions 15.11.x: upgrade to version 15.11.1 or later
  8. After upgrade, verify GitLab is running: `gitlab-rake gitlab:git:fsck`
Caveat Patch and minor version upgrades within the same major series are generally safe; ensure you review release notes for any configuration 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-2023-1178 — 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-2023-1178 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