GitLabApplication
CVE-2022-3758
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 affecting all versions starting from 15.5 before 15.7.8, all versions starting from 15.8 before 15.8.4, all versions starting from 15.9 before 15.9.2. Due to improper permissions checks an unauthorised user was able to read, add or edit a users private snippet.
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 confidenceGitLab versions 15.5 through 15.9.1 contain improper permission checks in the snippet functionality that allow unauthorized users to read, add, or edit private snippets belonging to other users. This is an authorization bypass vulnerability stemming from missing or insufficient access control validation.
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.5.0, < 15.7.8>= 15.8.0, < 15.8.4>= 15.9.0, < 15.9.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed GitLab versionLog into the GitLab admin area and navigate to the Dashboard or use the command 'gitlab-rake gitlab:env:info' on the server to retrieve the exact version numberAffected if The installed version falls within any of these ranges: 15.5.0 to 15.7.7, 15.8.0 to 15.8.3, or 15.9.0 to 15.9.1
-
Confirm snippet functionality is in useCheck if any snippets exist in the GitLab instance by visiting the Snippets page or querying the database for non-zero snippet countsAffected if Snippets have been created and stored in the instance, making the vulnerable code path reachable
-
Verify external or non-owner user accounts existReview the user directory in the Admin Area to determine if there are users other than administrators who could potentially access snippets they do not ownAffected if Multiple user accounts exist, particularly external or limited users who should not have access to private snippets belonging to other users
-
Test snippet access controls with a secondary accountCreate a private snippet with one test user, then attempt to access, modify, or delete that snippet using a different non-admin user account that should not have permissionAffected if The secondary account can read, add, or edit private snippets owned by another user, confirming the authorization bypass is present
A GitLab instance is affected if it runs any version from 15.5.0 through 15.9.1 and has multiple users with private snippets that should be restricted between them.
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.7.815.8.415.9.2
Upgrade GitLab to version 15.7.8, 15.8.4, or 15.9.2 or later. Alternatively, if immediate upgrade is not possible, review snippet access controls and consider restricting external user access to the instance.
Upgrade to GitLab 15.7.8, 15.8.4, or 15.9.2 (or later)
- Backup your GitLab instance data before proceeding with any upgrade
- Review the GitLab upgrade documentation for your specific installation method (Omnibus, source, etc.)
- Identify your current GitLab version to confirm it falls within the affected range: 15.5.0 to <15.7.8, 15.8.0 to <15.8.4, or 15.9.0 to <15.9.2
- Plan your upgrade path based on your current version - upgrade to the next available stable release within your version branch
- For installations using GitLab Omnibus: run 'apt-get update && apt-get install gitlab-ce' (or 'gitlab-ee' for Enterprise Edition)
- For source installations: follow the upgrade guide in GitLab documentation for upgrading from source
- After upgrade, verify the GitLab version matches the patched release (15.7.8, 15.8.4, or 15.9.2)
- Test that private snippet permissions are working correctly - unauthorized users should no longer be able to access private snippets
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3758 — 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-3758 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