GitLabApplication
CVE-2022-3067
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 the Import functionality of GitLab CE/EE affecting all versions starting from 14.4 before 15.2.5, all versions starting from 15.3 before 15.3.4, all versions starting from 15.4 before 15.4.1. It was possible for an authenticated user to read arbitrary projects' content given the project's ID.
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 confidenceThe Import functionality in GitLab CE/EE contains an Insecure Direct Object Reference (IDOR) vulnerability allowing authenticated users to read arbitrary project contents by knowing the project's ID, even without proper authorization to those projects.
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.4, < 15.2.5>= 15.3, < 15.3.4>= 15.4, < 15.4.1CVSS 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.
-
Determine installed GitLab versionCheck the version via the GitLab admin area (Help > Version), the API endpoint GET /api/v4/version, or the version file in the GitLab installation directoryAffected if The version falls within any of these ranges: >= 14.4 and < 15.2.5; >= 15.3 and < 15.3.4; >= 15.4 and < 15.4.1
-
Verify Import functionality is accessibleConfirm that authenticated users have access to the project Import feature. This is typically found in the project settings under Settings > General > Advanced > Import export, or via the /import_export endpointAffected if Authenticated users (including those without explicit project authorization) can access the Import functionality for projects they do not own or have permission to view
-
Check project import endpoint behaviorAs an authenticated user without access to a specific project, attempt to access the import endpoint for that project using its numeric project ID (e.g., GET /api/v4/projects/{project_id}/import_export)Affected if The API returns successful project import/export data or metadata for projects the user is not authorized to access, indicating the IDOR is present
You are affected if your GitLab version is in the affected ranges AND the Import feature is accessible to authenticated users without proper authorization checks on the target project.
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.2.515.3.415.4.1
Upgrade to GitLab 15.2.5, 15.3.4, 15.4.1 or later. Review and enforce project access controls to ensure users can only access projects they are explicitly authorized to view.
15.4.1 or later
- Upgrade GitLab to version 15.4.1 or later
- Alternatively, upgrade to 15.3.4 if staying on the 15.3 branch
- Alternatively, upgrade to 15.2.5 if staying on the 15.2 branch
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-3067 — 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-3067 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