GitLabApplication
CVE-2022-3285
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 · uneditedBypass of healthcheck endpoint allow list affecting all versions from 12.0 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1 allows an unauthorized attacker to prevent access to GitLab
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 healthcheck endpoint has an allow list mechanism intended to restrict access, but a vulnerability allows unauthorized attackers to bypass this restriction. By exploiting the bypass, an attacker can trigger the healthcheck endpoint in a way that causes denial of service, preventing legitimate access to the GitLab instance.
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.0.0, < 15.2.5>= 15.3.0, < 15.3.4= 15.4.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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the GitLab version check command available in your installation (such as gitlab-rake gitlab:env:info or consult your package manager), or locate the version file in your GitLab installation directoryAffected if The installed version falls within the affected ranges: 12.0.0 to 15.2.4, 15.3.0 to 15.3.4, or exactly 15.4.0
-
Verify healthcheck endpoint exposureIdentify the healthcheck endpoint URL in your GitLab instance (commonly /-/health, /health, or similar path depending on your configuration) and confirm it is accessible from network locations where untrusted users could reach itAffected if The healthcheck endpoint is accessible from untrusted network locations without proper authentication or network-level restrictions
-
Review healthcheck allow list configurationExamine your GitLab configuration files (gitlab.yml or similar) for the healthcheck allow list settings, checking whether specific IP addresses or networks have been defined to restrict accessAffected if The allow list is not configured, is empty, or contains overly permissive entries (such as 0.0.0.0/0 or ::/0) that would allow unrestricted access
You are affected if your GitLab version is one of the affected versions listed AND the healthcheck endpoint is accessible from untrusted network locations, particularly if the allow list is not properly configured to restrict access.
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 · scoped15.2.515.3.4
Upgrade GitLab to version 15.2.5 or later for the 15.2.x branch, 15.3.4 or later for the 15.3.x branch, or 15.4.1 or later for the 15.4.x branch. Alternatively, restrict network-level access to the healthcheck endpoint as a compensating control until patching is possible.
GitLab 15.4.1 or later (or 15.2.5+ / 15.3.4+ depending on your current branch)
- Backup your GitLab instance data and configuration
- Review GitLab upgrade documentation for your deployment method (Omnibus, source, etc.)
- Plan for maintenance window as upgrade will require service restart
- Stop GitLab services before upgrade
- Upgrade to GitLab 15.4.1 or later (15.2.5+ for 15.2.x line, 15.3.4+ for 15.3.x line)
- Verify healthcheck endpoint behaves as expected after upgrade
- Restart GitLab services
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3285 — 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-3285 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