dbcve.org
GitLabApplication

CVE-2023-0632

HIGH · 7.5 CVSS v3.1 Published 2023-08-02
Fix available
A fix is available. Upgrade to 16.0.8 / 16.1.3 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 15.2 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. A Regular Expression Denial of Service was possible by using crafted payloads to search Harbor Registry.

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

A Regular Expression Denial of Service (ReDoS) vulnerability exists in GitLab's Harbor Registry search functionality. Attackers can send specially crafted regex payloads that cause excessive computational consumption, potentially rendering the service unavailable.

MitigationUpgrade GitLab to version 16.0.8, 16.1.3, 16.2.2 or later to remediate this vulnerability.

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:>= 15.2, < 16.0.8>= 16.1, < 16.1.3>= 16.2, < 16.2.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
None
Integrity
None
Availability
High

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

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 installed GitLab version
    Access the GitLab admin dashboard and navigate to the Help section or use the /api/v4/version API endpoint to retrieve the running GitLab version
    Affected if The returned version falls within 15.2 to 16.0.7, 16.1.0 to 16.1.2, or 16.2.0 to 16.2.1
  2. Confirm Harbor Registry integration is active
    Check if Harbor Registry is enabled for any projects or at the instance level in GitLab under Project Settings > Container Registry or Admin Area > Harbor Settings
    Affected if Harbor Registry integration is configured and accessible in the GitLab instance
  3. Verify Harbor Registry search functionality is accessible
    Attempt to access the Harbor Registry search feature through the GitLab interface or API endpoint related to Harbor container registry search
    Affected if The search functionality is accessible and accepts regex-based search queries

A GitLab instance is affected if it runs a version between 15.2 and 16.0.7, 16.1.0 and 16.1.2, or 16.2.0 and 16.2.1 AND has Harbor Registry integration enabled with accessible search functionality.

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 16.0.8 / 16.1.3 / 16.2.2 or later
Fixed in 16.0.816.1.316.2.2
Interim mitigation

Upgrade GitLab to version 16.0.8, 16.1.3, 16.2.2 or later to remediate this vulnerability.

Recommended fix High confidence

Upgrade to 16.0.8 (or later 16.0.x), 16.1.3 (or later 16.1.x), or 16.2.2 (or later 16.2.x); ideally upgrade to the latest stable GitLab release

  1. 1. Identify current GitLab version by navigating to Admin Area > Dashboard or running `gitlab-rake gitlab:env:info`
  2. 2. Based on current version, determine the minimum safe upgrade target: if on 15.2-15.x upgrade to 16.0.8+, if on 16.1.x upgrade to 16.1.3+, if on 16.2.x upgrade to 16.2.2+
  3. 3. Back up the GitLab database and repository data before upgrading
  4. 4. Follow the official GitLab upgrade documentation for your installation method (Omnibus or source)
  5. 5. Stop GitLab services with `gitlab-ctl stop` (Omnibus) or stop the application server
  6. 6. Install the new package or update source code to the fixed version
  7. 7. Reconfigure GitLab with `gitlab-ctl reconfigure` (Omnibus) or run necessary database migrations
  8. 8. Start GitLab services with `gitlab-ctl start`
Caveat Review GitLab release notes for breaking changes between your current version and target version before upgrading

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

Fix this in GitLab Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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