GitLabApplication
CVE-2021-22192
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 from 13.2 allowing unauthorized authenticated users to execute arbitrary code on the server.
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 confidenceGitLab CE/EE versions 13.2 and later contain an authentication bypass vulnerability allowing any authenticated user (regardless of authorization level) to execute arbitrary code on the server through the web interface or API.
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
>= 13.2.0, < 13.7.9>= 13.8.0, < 13.8.6>= 13.9.0, < 13.9.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Check installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or access the GitLab web interface and navigate to Help > Version or Admin Area > Settings > GeneralAffected if The version displayed falls within 13.2.0 to 13.7.8, 13.8.0 to 13.8.5, or 13.9.0 to 13.9.3
-
Confirm user authentication is enabledVerify that the instance has internal authentication enabled or uses an external auth provider by checking Admin Area > Settings > General > Sign-up restrictions and AuthenticationAffected if User sign-up or external authentication is allowed, allowing any user to obtain valid credentials
-
Check for API accessVerify that the API is accessible (default on most installations) by attempting to reach /api/v4/version or checking Admin Area > Settings > APIAffected if The API is accessible and allows authenticated requests from any registered user
The environment is affected if the installed GitLab version falls within the affected ranges (13.2.0-13.7.8, 13.8.0-13.8.5, or 13.9.0-13.9.3) and the instance allows any user to obtain authentication credentials.
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 · scoped13.7.913.8.613.9.4
Upgrade GitLab to the patched version as specified in the official GitLab security release. Restrict network access to GitLab instances while pending updates.
GitLab 13.9.4 or later (preferably 13.10.0+)
- 1. Back up your GitLab instance data and configuration
- 2. Stop the GitLab service
- 3. Update GitLab to version 13.9.4 or later (13.10.0 or newer recommended)
- 4. Run 'gitlab-ctl reconfigure' to apply changes
- 5. Restart the GitLab service with 'gitlab-ctl restart'
- 6. Verify the upgrade was successful by checking the GitLab version
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 / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22192 — 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-22192 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