GitLabApplication
CVE-2022-2455
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 · uneditedA business logic issue in the handling of large repositories in all versions of GitLab CE/EE from 10.0 before 15.1.6, all versions starting from 15.2 before 15.2.4, all versions starting from 15.3 before 15.3.2 allowed an authenticated and authorized user to exhaust server resources by importing a malicious project.
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 confidenceA business logic flaw in GitLab's project import functionality allowed authenticated users to import specially crafted malicious projects that caused excessive resource consumption, leading to denial of service through server resource exhaustion.
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
>= 10.0.0, < 15.1.6>= 15.2, < 15.2.4>= 15.3, < 15.3.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 GitLab versionRun 'sudo gitlab-rake gitlab:env:info' on the GitLab server or check /opt/gitlab/version fileAffected if Installed version falls within 10.0.0 to 15.1.5, 15.2.0 to 15.2.3, or 15.3.0 to 15.3.1
-
Confirm project import feature is activeNavigate to Admin Area > Settings > General > Import and export settings, or inspect gitlab.yml configuration for import_sources parameterAffected if Import sources are enabled on an affected GitLab version
-
Review import job resource usageCheck Sidekiq logs or GitLab admin panel > Background Jobs > Queues for ProjectImportWorker jobs with unusually high memory or CPU consumptionAffected if Import jobs show excessive resource consumption patterns that exceed normal large repository imports
The environment is affected if GitLab version is 10.0.0 to <15.1.6, 15.2 to <15.2.4, or 15.3 to <15.3.2 AND the project import feature is enabled.
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.1.615.2.415.3.2
Upgrade GitLab to version 15.1.6, 15.2.4, 15.3.2 or later to receive the patched code that properly validates and handles large repository imports.
15.3.2, 15.2.4, or 15.1.6 (depending on which branch you are on)
- Backup your GitLab instance data before proceeding with any upgrade
- Identify your current GitLab version by running `gitlab-rake gitlab:env:info`
- If running 15.3.x, upgrade to 15.3.2 or later
- If running 15.2.x, upgrade to 15.2.4 or later
- If running 15.1.x, upgrade to 15.1.6 or later
- If running 10.0.0 to 15.0.x, upgrade to 15.1.6 first (following GitLab upgrade path documentation), then to latest stable
- After upgrade, verify GitLab is operational with `gitlab-rake gitlab:check`
- Confirm the vulnerability is resolved by importing a test project or verifying the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2455 — 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-2455 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