GitLabApplication
CVE-2021-22210
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. When querying the repository branches through API, GitLab was ignoring a query parameter and returning a considerable amount of results.
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 confidenceIn GitLab CE/EE versions 13.2 and later, the repository branches API endpoint ignores a query parameter (likely a limit/filter parameter), causing it to return significantly more results than intended. This leads to unintended information disclosure through API responses.
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.9.7>= 13.10.0, < 13.10.4>= 13.11.0, < 13.11.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 installed GitLab versionRun 'gitlab-rake gitlab:env:info' (Omnibus/Docker) or check version file for source installations. Alternatively, access the GitLab admin area and view the version information in the help section or run 'cat /opt/gitlab/version' for Omnibus installs.Affected if The installed version falls within any of these ranges: >= 13.2.0 and < 13.9.7, OR >= 13.10.0 and < 13.10.4, OR >= 13.11.0 and < 13.11.2
-
Verify API endpoint accessibilityEnsure you have API access credentials (personal access token) and can make requests to the GitLab API. The vulnerable endpoint is /api/v4/projects/:id/repository/branchesAffected if The GitLab instance has API access enabled and you can authenticate to it
-
Test for parameter ignoringMake two API requests to the branches endpoint: first with a small limit (e.g., per_page=1), then with a larger limit (e.g., per_page=100). Compare the number of results returned in each response. If both return the same large number of branches, the parameter is being ignored.Affected if The API returns significantly more branches than the limit specified in the query parameter, indicating the parameter is being ignored
Your GitLab instance is affected if it is running a version between 13.2.0 and 13.9.7, between 13.10.0 and 13.10.4, or between 13.11.0 and 13.11.2 AND the branches API returns more results than the per_page parameter specifies.
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.9.713.10.413.11.2
Upgrade GitLab to the patched version (14.x and later contain the fix). No client-side configuration can remediate this server-side code defect.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22210 — 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-22210 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