GitLabApplication
CVE-2022-2512
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 · uneditedAn issue has been discovered in GitLab CE/EE affecting all versions starting from 15.0 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. Membership changes are not reflected in TODO for confidential notes, allowing a former project members to read updates via TODOs.
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 confidenceIn affected GitLab versions, when a user is removed from a project, their TODO items referencing confidential notes are not properly invalidated. This allows former project members to continue receiving TODO notifications about confidential notes they should no longer have access to, resulting in unauthorized information disclosure.
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
>= 15.0.0, < 15.0.5>= 15.1.0, < 15.1.4= 15.2CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check GitLab versionRun `gitlab-rake gitlab:env:info` or navigate to the GitLab admin panel under 'Help' > 'Version' to determine the installed versionAffected if Version is 15.0.0 through 15.0.4, 15.1.0 through 15.1.3, or exactly 15.2 (these versions are vulnerable)
-
Identify confidential notes with TODO itemsUse the GitLab API endpoint `/todos` or check in the UI under 'To-Do List' to see if there are any TODO items pointing to confidential notes or confidential issuesAffected if Active TODO items exist for confidential notes that users should no longer access
-
Check for users removed from projects with confidential contentReview project audit logs in the admin panel under 'Audit Events' or use the API to query project member changes, looking for users who were removed from projects that contained confidential notesAffected if Users were removed from projects after having TODO items related to confidential notes or issues
If the GitLab version falls within 15.0.0-15.0.4, 15.1.0-15.1.3, or 15.2 AND there are active TODO items for confidential notes belonging to users no longer in the project, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 · scoped15.0.515.1.4
Upgrade GitLab to version 15.0.5, 15.1.4, 15.2.1, or later to receive the patch that properly invalidates TODO items for confidential notes when membership is revoked.
15.2.1 (or 15.0.5+ for 15.0.x branches, 15.1.4+ for 15.1.x branches)
- 1. Back up your GitLab instance data and configuration
- 2. Plan a maintenance window for the upgrade process
- 3. For GitLab 15.0.x: Upgrade to version 15.0.5 or later
- 4. For GitLab 15.1.x: Upgrade to version 15.1.4 or later
- 5. For GitLab 15.2.x: Upgrade to version 15.2.1 or later
- 6. Verify the upgrade completed successfully and test that TODO notifications for confidential notes now properly respect membership changes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2512 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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