dbcve.org
GitLabApplication

CVE-2023-6033

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-01
Fix available
A fix is available. Upgrade to 16.4.3 / 16.5.3 or later.
See remediation →
58/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
Improper neutralization of input in Jira integration configuration in GitLab CE/EE, affecting all versions from 15.10 prior to 16.6.1, 16.5 prior to 16.5.3, and 16.4 prior to 16.4.3 allows attacker to execute javascript in victim's browser.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in GitLab's Jira integration configuration. The Jira integration settings fail to properly sanitize input fields, allowing an attacker to inject malicious JavaScript that executes when other users view the Jira integration configuration page in their browsers.

MitigationUpgrade GitLab to version 16.6.1, 16.5.3, 16.4.3 or later. Until upgraded, limit access to Jira integration configuration settings to trusted administrators only.

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.10, < 16.6.1>= 16.4.0, < 16.4.3>= 16.5.0, < 16.5.3

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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
    Navigate to the GitLab Admin Area, then go to the Help page to view the version information. Alternatively, access the GitLab Rails console and run `puts Gitlab::VERSION` to retrieve the exact installed version number
    Affected if Version is 15.10.0 to 16.6.0, 16.4.0 to 16.4.2, or 16.5.0 to 16.5.2 (these ranges fall within the vulnerable versions)
  2. Verify Jira integration is enabled
    Navigate to Admin Area > Settings > Integrations > Jira, or for project-level integration go to a specific project Settings > Integrations > Jira. Check whether the Jira integration is turned on or has any saved configuration
    Affected if Jira integration is enabled or has any configuration saved in GitLab
  3. Check who can access Jira integration settings
    Review project and group membership to identify which users have the Maintainer or Owner role, as these roles typically grant permission to modify Jira integration settings. Also check group and project settings for any custom access configurations
    Affected if Users other than trusted administrators have access to configure Jira integration settings

You are affected if your GitLab version falls within one of the vulnerable ranges AND the Jira integration is enabled with users beyond trusted administrators able to access its configuration.

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.4.3 / 16.5.3 / 16.6.1 or later
Fixed in 16.4.316.5.316.6.1
Interim mitigation

Upgrade GitLab to version 16.6.1, 16.5.3, 16.4.3 or later. Until upgraded, limit access to Jira integration configuration settings to trusted administrators only.

Recommended fix High confidence

Upgrade to GitLab 16.6.1 or later (16.6.x series)

  1. Identify your current GitLab version using `gitlab-rake gitlab:env:info`
  2. Review the GitLab upgrade documentation for your current version to the target version at https://docs.gitlab.com/ee/update/
  3. Create a full backup of your GitLab instance using `gitlab-backup-create`
  4. Stop GitLab services with `gitlab-ctl stop`
  5. For packaged installations, update the package repository and install: `sudo apt-get update && sudo apt-get install gitlab-ee` (Debian/Ubuntu) or `sudo yum install gitlab-ee` (RHEL/CentOS)
  6. For self-compiled installations, clone the target version from https://gitlab.com/gitlab-org/gitlab-ce and follow upgrade instructions
  7. Start GitLab services with `gitlab-ctl start`
  8. Run `gitlab-rake gitlab:check` to verify the upgrade was successful
Caveat Review GitLab 16.6 release notes for any breaking changes; major version upgrades may require database migrations that take significant time

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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