GitLabApplication
CVE-2022-1431
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 affecting all versions starting from 12.10 before 14.8.6, all versions starting from 14.9 before 14.9.4, all versions starting from 14.10 before 14.10.1. GitLab was not correctly handling malicious requests to the PyPi API endpoint allowing the attacker to cause uncontrolled 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 · moderate confidenceGitLab versions 12.10 through 14.10.1 contain a vulnerability in the PyPi API endpoint where malicious requests are not properly validated, allowing attackers to cause uncontrolled resource consumption and potentially render the service unavailable.
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
>= 12.10.0, < 14.8.6>= 14.9.0, < 14.9.4= 14.10.0CVSS 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.
-
Check installed GitLab versionRun `gitlab-rake gitlab:version` from the GitLab server console, or log into the GitLab Admin Area and check the version shown on the home pageAffected if The version falls within any of these ranges: 12.10.0 to 14.8.5, 14.9.0 to 14.9.3, or exactly 14.10.0
-
Confirm PyPi repositories are enabledLog into GitLab as an administrator, navigate to Admin Area > Settings > Repository > and locate the 'PyPI' settings section. Check if the feature toggle is enabled.Affected if The PyPi feature is turned ON in GitLab settings
-
Verify PyPi API endpoint is accessibleAttempt to access the PyPi API endpoint for any project: make a HEAD request to `/api/v4/projects/1/pypi` or similar project-level PyPi endpointAffected if The endpoint responds (returns 200 or 404 rather than 403/401), indicating the feature is active
-
Check for abnormal API request patternsReview GitLab logs (typically in /var/log/gitlab/gitlab-rails/production.log) for repeated or bulk requests to `/api/v4/projects/*/pypi` endpoints within a short time windowAffected if Logs show high-volume or repetitive PyPi API requests that could indicate exploitation attempts
You are affected if your GitLab version is 12.10.0-14.8.5, 14.9.0-14.9.3, or 14.10.0 AND the PyPi repository feature is enabled in your instance.
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.8.614.9.4
Upgrade GitLab to version 14.8.6, 14.9.4, 14.10.1 or later to patch the vulnerability. Consider implementing rate limiting on API endpoints as a defense-in-depth measure.
14.10.1 (or 14.8.6/14.9.4 depending on your current branch)
- Back up your GitLab instance data and configuration
- Upgrade GitLab to version 14.8.6 or later (if currently on 14.8.x or earlier)
- If running 14.9.x, upgrade to version 14.9.4 or later
- If running 14.10.0, upgrade to version 14.10.1 or later
- Verify the upgrade was successful by checking the GitLab admin area
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-1431 — 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-1431 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