GitLabApplication
CVE-2018-18843
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 · uneditedThe Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4.4 has SSRF.
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 confidenceServer-Side Request Forgery (SSRF) vulnerability in the Kubernetes integration of GitLab Enterprise Edition allows attackers to make the GitLab server perform unauthorized requests to internal resources or 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
>= 11.0.0, < 11.2.8>= 11.3.0, < 11.3.9>= 11.4.0, < 11.4.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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Determine installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or access the GitLab admin dashboard and navigate to the About page (typically /admin/about) to find the exact version numberAffected if The version is 11.0.0 through 11.2.7, 11.3.0 through 11.3.8, or 11.4.0 through 11.4.3 (any version less than 11.2.8, 11.3.9, or 11.4.4 within the 11.x releases)
-
Confirm Kubernetes integration is activeCheck if any project, group, or the GitLab instance has a Kubernetes service configured. This can be done via the UI at Project Settings > Integrations > Kubernetes, or by reviewing the database table `services` for entries with `type` set to `KubernetesService`Affected if The Kubernetes integration is enabled or has been configured for any project, group, or at the instance level
You are affected only if running a vulnerable GitLab version (11.0.0-11.2.7, 11.3.0-11.3.8, or 11.4.0-11.4.3) AND the Kubernetes integration feature is currently or was previously 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.
dbcve · scoped11.2.811.3.911.4.4
Upgrade GitLab Enterprise Edition to version 11.2.8, 11.3.9, 11.4.4 or later to resolve the SSRF vulnerability in the Kubernetes integration.
11.4.4 (or any version >= 11.4.4)
- Back up your GitLab database and repository data before starting the upgrade
- Ensure your system meets the requirements for the target version
- For GitLab installations using Omnibus: run 'sudo gitlab-ctl stop' to stop GitLab services
- For Omnibus installations: download and install the appropriate package for your OS from GitLab's package repository
- For the specific fixed version, install either 11.2.8, 11.3.9, or 11.4.4 (11.4.4 recommended as it includes all fixes)
- Run 'sudo gitlab-ctl reconfigure' to apply the configuration
- Run 'sudo gitlab-ctl start' to start GitLab services
- Verify the upgrade was successful by checking GitLab version at /help or via 'sudo gitlab-rake gitlab:env:info'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18843 — 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-2018-18843 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