GitLabApplication
CVE-2022-1121
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 lack of appropriate timeouts in GitLab Pages included in GitLab CE/EE all versions prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allows an attacker to cause unlimited resource consumption.
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 Pages lacks appropriate timeout controls, allowing attackers to trigger unlimited resource consumption and cause denial of service by establishing connections that never terminate.
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.7.7>= 14.8.0, < 14.8.5>= 14.9.0, < 14.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 the installed GitLab versionRun 'gitlab-rake gitlab:env:info' from the GitLab server console, or check the Admin Area > Dashboard in the web UI under the version indicatorAffected if The displayed version is below 14.7.7, between 14.8.0 and 14.8.5, or between 14.9.0 and 14.9.2
-
Verify if GitLab Pages is enabledCheck the gitlab.rb configuration file for 'pages_external_url' setting, or inspect the Pages section in Admin Area > Settings > PagesAffected if Pages is enabled and an external URL is configured, meaning the Pages daemon is running and vulnerable to connection exhaustion
-
Confirm the Pages daemon is accessibleAttempt to reach the configured Pages external URL over HTTP/HTTPS or check if the Pages service is listening on port 8090 or the configured portAffected if The Pages site responds to requests, indicating the vulnerable component is exposed
You are affected if GitLab Pages is enabled and your installed version falls within the affected ranges: < 14.7.7, 14.8.0-14.8.5, or 14.9.0-14.9.2
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 · scoped14.7.714.8.514.9.2
Update GitLab to version 14.7.7, 14.8.5, 14.9.2 or later to receive the timeout configuration patches.
14.9.2 or later (or 14.8.5 / 14.7.7 for respective branches)
- Back up your GitLab instance database and repository data before upgrading
- Ensure your system meets the requirements for the target GitLab version
- Upgrade GitLab to version 14.9.2 or later (or 14.8.5 if staying on 14.8.x, or 14.7.7 if staying on 14.7.x)
- After upgrade, verify GitLab Pages service is running correctly
- Test that GitLab Pages sites are accessible and functioning properly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1121 — 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-1121 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