GitLabApplication
CVE-2021-22214
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 · uneditedWhen requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab CE/EE affecting all versions starting from 10.5 was possible to exploit for an unauthenticated attacker even on a GitLab instance where registration is limited
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 confidenceThis is a server-side request forgery (SSRF) vulnerability in GitLab's webhook functionality. When requests to internal networks for webhooks are enabled, an unauthenticated attacker can cause the GitLab server to make arbitrary requests to internal network resources, potentially accessing sensitive internal services.
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.5, < 13.10.5>= 13.11, < 13.11.5>= 13.12, < 13.12.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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Check installed GitLab versionAccess GitLab Admin area > Help > GitLab version, or run 'gitlab-rake gitlab:env:info' from the server consoleAffected if The version is >= 10.5 and < 13.10.5, OR >= 13.11 and < 13.11.5, OR >= 13.12 and < 13.12.2
-
Confirm webhook functionality is in useNavigate to a project or group settings, or query the database for webhooks table entries - check if any webhooks are configuredAffected if Any webhooks exist in the GitLab instance
-
Inspect internal network setting for webhooksGo to Admin area > Settings > Network > Outbound requests, or check the 'allow_requests_to_the_internal_network' setting via API or databaseAffected if The 'Allow requests to the internal network' checkbox is enabled for webhooks
-
Verify webhook URL destinationsReview existing webhook URLs to see if any point to internal network addresses (e.g., 10.x.x.x, 192.168.x.x, localhost, or RFC 1918 ranges)Affected if Any configured webhook URLs target internal network addresses
A user is affected if their GitLab version falls within the vulnerable ranges AND webhooks are configured with the internal network request allowance 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.
From vendor data13.10.513.11.513.12.2
Disable the 'allow requests to the internal network' setting for webhooks in GitLab settings, or upgrade to a patched GitLab version.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22214 — 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-2021-22214 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