GitLabApplication
CVE-2022-0244
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 with 14.5. Arbitrary file read was possible by importing a group was due to incorrect handling of file.
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 · moderate confidenceArbitrary file read vulnerability in GitLab CE/EE affecting all versions starting with 14.5. The issue stems from incorrect file handling during group import functionality, allowing authenticated attackers to read arbitrary files on the server file system.
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
>= 14.5, <= 14.5.3>= 14.6, <= 14.6.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Determine installed GitLab versionRun command: gitlab-rake gitlab:env:info or check /opt/gitlab/version-manifest.txt, or look at the admin area dashboardAffected if Version is 14.5.0 to 14.5.3 OR 14.6.0 to 14.6.2
-
Verify group import feature is accessibleCheck if any authenticated user can access Group > New Group > Import group > From GitLab project export file. The vulnerability requires the group import functionality to be available.Affected if Group import is enabled and users can import groups (feature exists in GitLab CE/EE by default in affected versions)
-
Confirm user authentication is possibleReview whether there are any local users, LDAP/SSO users, or other authenticated accounts on the GitLab instance.Affected if At least one authenticated user exists who could access the group import feature
If the GitLab version falls within 14.5.0-14.5.3 or 14.6.0-14.6.2 AND the group import feature is accessible to authenticated users, the instance is vulnerable to arbitrary file read via the group import functionality.
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 · scopedUpgrade GitLab to the latest patched version. If immediate upgrade is not possible, restrict or disable group import functionality for untrusted users as a temporary workaround.
GitLab 14.6.3 or later, or 14.7.0 or later
- 1. Back up your GitLab instance data and configuration
- 2. Plan for downtime during the upgrade process
- 3. Upgrade GitLab to version 14.6.3 or later (or 14.7.0 or later for the latest features)
- 4. Verify the upgrade was successful by checking the GitLab administration area
- 5. Test that the group import functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0244 — 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-0244 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