dbcve.org
GitLabApplication

CVE-2022-2281

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 information disclosure vulnerability in GitLab EE affecting all versions from 12.5 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1, allows disclosure of release titles if group milestones are associated with any project releases.

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

An information disclosure vulnerability in GitLab EE allows unauthorized disclosure of release titles when group milestones are improperly associated with project releases. This is an access control flaw where release metadata is exposed beyond its intended visibility scope.

MitigationUpgrade GitLab to version 14.10.5, 15.0.4, or 15.1.1 or later to remediate this information disclosure 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:>= 12.5.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 `sudo gitlab-rake gitlab:env:info` or check the Admin Area > Settings > General page. Alternatively, check the /opt/gitlab/version file or run `gitlab --version`.
    Affected if The version falls within < 14.10.5, or >= 15.0.0 and < 15.0.4, or equals 15.1.0.
  2. Identify releases linked to group milestones
    Query the GitLab database or API: `GET /projects/:id/releases` and check the `milestone` field. Cross-reference any release milestones against the group milestones API endpoint: `GET /groups/:id/milestones`. Identify releases where the associated milestone belongs to a parent group rather than the project itself.
    Affected if Any project release is associated with a group milestone rather than a project-specific milestone.
  3. Verify visibility of affected releases
    Check the project and group visibility settings at Settings > General > Visibility. Then attempt to access the release information from an account that is not a member of the group owning the milestone but has some project access. Use the API: `GET /projects/:id/releases/:tag_name` with a low-privilege user token.
    Affected if Release titles are visible to users who should not have access to the group milestone information.
  4. Review group milestone access controls
    In the Admin Area, navigate to the Groups section and review the group(s) whose milestones are linked to project releases. Check Settings > Member permissions for each group. Verify whether the group milestone is set to a more restrictive access level than the project release.
    Affected if Group milestones linked to releases have broader visibility than intended, exposing release metadata to unauthorized users.

A user is affected if their GitLab version is in the vulnerable range AND any project release is associated with a group milestone, allowing unauthorized disclosure of release titles to users lacking proper group access.

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, or 15.1.1 or later to remediate this information disclosure vulnerability.

Recommended fix High confidence

14.10.5+, 15.0.4+, or 15.1.1+ (latest stable release recommended)

  1. 1. Back up your GitLab instance data and configuration
  2. 2. Ensure you have a valid backup before proceeding with the upgrade
  3. 3. For GitLab 14.x: Upgrade to version 14.10.5 or later (recommended: latest 14.x stable)
  4. 4. For GitLab 15.0.x: Upgrade to version 15.0.4 or later (recommended: latest 15.0.x stable)
  5. 5. For GitLab 15.1.x: Upgrade to version 15.1.1 or later (recommended: latest 15.1.x stable)
  6. 6. After upgrade, verify that group milestones associated with project releases no longer expose release titles to unauthorized users
  7. 7. Review user permissions on projects using group milestones to confirm the fix is effective
Caveat Review GitLab upgrade guides for version-specific breaking changes between your current version and target version; major version jumps may require additional migration steps

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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