GitLabApplication
CVE-2019-11605
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 was discovered in GitLab Community and Enterprise Edition 11.8.x before 11.8.10, 11.9.x before 11.9.11, and 11.10.x before 11.10.3. It allows Information Disclosure. A small number of GitLab API endpoints would disclose project information when using a read_user scoped token.
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 confidenceA small number of GitLab API endpoints improperly disclosed project information when accessed with read_user scoped tokens. The read_user scope is intended to provide limited access to user-specific data, but certain endpoints were returning project-related information that should not have been accessible at that privilege level.
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.8.0, < 11.8.10>= 11.9.0, < 11.9.11>= 11.10.0, < 11.10.3CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 the installed GitLab versionRun `gitlab-rake gitlab:env:info` or check the GitLab admin panel under the Help section to see the exact version numberAffected if The version falls within any of these ranges: 11.8.0 to 11.8.9, 11.9.0 to 11.9.10, or 11.10.0 to 11.10.2
-
Determine if read_user scoped API tokens are in useReview any API integrations or scripts that authenticate to this GitLab instance and check if they request or use tokens with the read_user scopeAffected if Read_user scoped tokens exist and are actively being used against the GitLab API
-
Identify API calls returning unexpected project dataAudit API access logs or test endpoints using a read_user scoped token to see if project names, paths, or other project-related fields appear in responses from user-profile endpointsAffected if API responses from user-level endpoints contain project information that should not be accessible at the read_user privilege level
You are affected if your GitLab version is 11.8.0-11.8.9, 11.9.0-11.9.10, or 11.10.0-11.10.2 AND you have API tokens using the read_user scope in use
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.8.1011.9.1111.10.3
Upgrade GitLab to version 11.8.10, 11.9.11, or 11.10.3 or later to resolve the improper information disclosure via read_user scoped API tokens.
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-2019-11605 — 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-2019-11605 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