GitLabApplication
CVE-2018-19577
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 · uneditedGitlab CE/EE, versions 8.6 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an incorrect access control vulnerability that displays to an unauthorized user the title and namespace of a confidential issue.
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 confidenceGitLab CE/EE versions 8.6 through 11.x contain an incorrect access control vulnerability where unauthorized users can view the title and namespace of confidential issues. This is an information disclosure flaw stemming from improper authorization checks when accessing issue data.
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
>= 8.6.0, < 11.3.11>= 11.4.0, < 11.4.8>= 11.5.0, < 11.5.1CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Identify installed GitLab versionRun `gitlab-rake gitlab:env:info` or check the GitLab admin dashboard under 'Help' > 'Version' to find the exact version numberAffected if Version falls within 8.6.0 to 11.3.10, 11.4.0 to 11.4.7, or 11.5.0 to 11.5.0 (i.e., 8.6.0 <= version < 11.3.11 OR 11.4.0 <= version < 11.4.8 OR 11.5.0 <= version < 11.5.1)
-
Confirm confidential issues feature is in useNavigate to any project repository, go to Issues > List view, and look for any issues marked as 'confidential' in the issue list or check project settings for issue visibilityAffected if Any project contains confidential issues and the GitLab version is in the affected range
-
Verify unauthorized user access potentialAs a non-member user (or anonymous if public projects), attempt to access issues via the API endpoint or UI for a project that contains confidential issues, or review project member settings to confirm external or non-member users have project accessAffected if Non-member or external users can potentially view issue data and the GitLab version is vulnerable
You are affected if your GitLab version is within the vulnerable ranges (8.6.0 through 11.3.10, 11.4.0 through 11.4.7, or 11.5.0) AND your instance has projects with confidential issues accessible to non-member users.
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 data11.3.1111.4.811.5.1
Upgrade GitLab to version 11.3.11, 11.4.8, 11.5.1 or later to patch the access control vulnerability.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19577 — 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-19577 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