dbcve.org
GitLabApplication

CVE-2022-1999

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-01
Fix available
A fix is available. Upgrade to 14.10.5 / 15.0.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 issue has been discovered in GitLab CE/EE affecting all versions from 8.13 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1. Under certain conditions, using the REST API an unprivileged user was able to change labels description.

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 CE/EE contains a broken access control vulnerability in its REST API where an unprivileged user (such as a guest or basic user) could modify label descriptions that should be restricted to higher-privileged users. This represents an authorization bypass allowing unauthorized modification of project metadata.

MitigationUpgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later. Alternatively, restrict API access and audit existing user permissions until the upgrade can be completed.

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.13.0, < 14.10.5>= 15.0.0, < 15.0.4= 15.1.0

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 package version with 'rpm -q gitlab-ce' for RHEL/CentOS or 'dpkg -l | grep gitlab' for Debian/Ubuntu
    Affected if Version is >= 8.13.0 and < 14.10.5, OR >= 15.0.0 and < 15.0.4, OR equals 15.1.0
  2. Verify API is accessible
    Check if the API is enabled by reviewing /opt/gitlab/gitlab-rails/working/rack_attack.rb or accessing the /api/v4/version endpoint externally
    Affected if API endpoints respond to requests (indicating API is enabled)
  3. Confirm unprivileged user API access
    Attempt to access the API with a guest or basic user account credentials via curl to GET /api/v4/projects/:id/labels and verify the response
    Affected if Unauthenticated or unprivileged (guest/basic) users can successfully query the API endpoint

If the installed GitLab version falls within the affected ranges and the REST API is accessible to unprivileged users, the environment is vulnerable to CVE-2022-1999

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 14.10.5 / 15.0.4 or later
Fixed in 14.10.515.0.4
Interim mitigation

Upgrade GitLab to version 14.10.5, 15.0.4, 15.1.1 or later. Alternatively, restrict API access and audit existing user permissions until the upgrade can be completed.

Recommended fix High confidence

GitLab 14.10.5, 15.0.4, or 15.1.1 (or latest stable release in your minor line)

  1. 1. Back up your GitLab instance database and repository data
  2. 2. Check your current GitLab version in Admin Area > Metrics and Profiling > Version
  3. 3. Plan maintenance window as upgrades may require downtime
  4. 4. For GitLab 14.x (8.13.0 to <14.10.5): Upgrade to 14.10.5 or later (preferably latest 14.x)
  5. 5. For GitLab 15.0.x (<15.0.4): Upgrade to 15.0.4 or later (preferably latest 15.0.x)
  6. 6. For GitLab 15.1.0: Upgrade to 15.1.1 or later (preferably latest 15.1.x or jump to 15.2+)
  7. 7. After upgrade, verify the fix by confirming unprivileged users cannot modify label descriptions via REST API
  8. 8. Review Admin Area > Labels to confirm existing labels are intact
Caveat GitLab upgrades may require database migrations; review release notes for breaking changes between minor versions, especially when crossing major version boundaries (14.x to 15.x)

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-2022-1999 — 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-1999 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