dbcve.org
GitLabApplication

CVE-2022-3066

MEDIUM · 5.4 CVSS v3.1 Published 2022-10-17
Fix available
A fix is available. Upgrade to 15.2.5 / 15.3.4 or later.
See remediation →
60/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 in GitLab affecting all versions starting from 10.0 before 15.2.5, all versions starting from 15.3 before 15.3.4, all versions starting from 15.4 before 15.4.1. It was possible for an unauthorised user to create issues in a project.

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 15.2.x before 15.2.5, 15.3.x before 15.3.4, and 15.4.x before 15.4.1 contain an authorization bypass where unauthenticated or unauthorized users could create issues in projects where they lack proper permissions.

MitigationUpgrade GitLab to version 15.2.5, 15.3.4, or 15.4.1 or later. If immediate upgrade is not possible, restrict project creation permissions and audit existing access controls.

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:>= 10.0.0, < 15.2.5>= 15.3, < 15.3.4>= 15.4, < 15.4.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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Determine installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the omnibus package version with `gitlab-ctl version`. For Docker, check the image tag or run `cat /opt/gitlab/version-manifest.txt`. Compare the version number to the affected ranges: 15.2.x before 15.2.5, 15.3.x before 15.3.4, or 15.4.x before 15.4.1.
    Affected if The installed version falls within any of the affected version ranges.
  2. Verify issue creation settings
    Navigate to Admin Area > Settings > Visibility and access control (or /admin/settings/visibility_and_access_controls). Look for settings controlling who can create issues: options like 'Project users', 'Project members', 'Developers + Maintainers', or settings permitting external/unauthenticated users to create issues.
    Affected if The instance allows unauthenticated users or users without proper project membership to create issues.
  3. Check project-level issue creation permissions
    For individual projects, go to Project Settings > Permissions. Review the 'Issues' row under 'Project features' to see if issues are enabled and which roles can create them. Check if any public or internal projects have overly permissive issue creation settings.
    Affected if Projects have issue creation enabled for roles that should not have permission based on the project's access control settings.
  4. Audit external user issue creation access
    Review any external users or external groups configured in the instance. Verify whether external users have been granted the ability to create issues in projects where they are not members. Check /admin/users with 'External' filter and review their project memberships.
    Affected if External users can create issues in projects without being members, or without proper authorization.

Your GitLab instance is affected if it runs a version within 15.2.x < 15.2.5, 15.3.x < 15.3.4, or 15.4.x < 15.4.1 AND has issue creation enabled for unauthenticated or unauthorized users.

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.2.5 / 15.3.4 / 15.4.1 or later
Fixed in 15.2.515.3.415.4.1
Interim mitigation

Upgrade GitLab to version 15.2.5, 15.3.4, or 15.4.1 or later. If immediate upgrade is not possible, restrict project creation permissions and audit existing access controls.

Recommended fix High confidence

15.2.5, 15.3.4, 15.4.1, or later

  1. 1. Back up your GitLab instance database and configuration before proceeding with the upgrade.
  2. 2. Review the GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart).
  3. 3. Ensure your current GitLab version is one of the affected versions: 10.0.0 through 15.2.4, 15.3.x through 15.3.3, or 15.4.x.
  4. 4. Plan your upgrade path: if upgrading across multiple minor versions, upgrade incrementally (e.g., 15.2.x to 15.3.x to 15.4.x).
  5. 5. For GitLab Omnibus installations, run: sudo gitlab-ctl stop && sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee).
  6. 6. For source installations, follow the GitLab upgrade guide to install the required dependencies and run the migration scripts.
  7. 7. After upgrade, verify the GitLab version matches the target fixed version using: sudo gitlab-rake gitlab:env:info.
  8. 8. Start GitLab services: sudo gitlab-ctl start.
Caveat Major version upgrades may require database migrations and additional downtime; review GitLab upgrade guides for specific version jump risks

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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