GitLabApplication
CVE-2024-1539
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 EE affecting all versions starting from 15.2 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. It was possible to disclose updates to issues to a banned group member using the API.
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 EE versions prior to 16.9.7, 16.10.5, and 16.11.2 contain an information disclosure vulnerability where the API incorrectly allowed banned group members to receive updates about issues they should no longer have access to. This is an authorization bypass in the issue update notification API.
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
>= 15.2.0, < 16.9.7>= 16.10.0, < 16.10.5>= 16.11.0, < 16.11.2CVSS 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 EE versionRun 'gitlab-rake gitlab:env:info' or check the GitLab admin panel under Help > Version to retrieve the currently running GitLab EE version numberAffected if The installed version falls within any of these ranges: 15.2.0 to 16.9.6, 16.10.0 to 16.10.4, or 16.11.0 to 16.11.1
-
Review group membership for banned usersIn GitLab admin area, navigate to Groups > select each group > Members tab, and identify any users with 'Banned' status in the member listAffected if Any groups contain members marked as Banned who previously had access to sensitive issues
-
Verify banned user access to issue notificationsUsing the GitLab API with a banned user's credentials, attempt a GET request to the issue updates endpoint (e.g., /api/v4/projects/:id/issues/:issue_id) for an issue in a group where the user was bannedAffected if The banned user can retrieve issue details or receives notification webhooks/emails about issues they should no longer access
-
Check audit logs for unauthorized issue accessReview GitLab audit logs under Admin Area > Monitoring > Audit Events, filtering for events from banned user accounts accessing issue-related API endpointsAffected if Audit logs show banned users successfully accessing issue data via API after being banned from groups
You are affected if your GitLab EE version is below 16.9.7 (or between 16.10.0-16.10.4, or between 16.11.0-16.11.1) AND you have banned users in groups that contain issues they should no longer 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 · scoped16.9.716.10.516.11.2
Upgrade GitLab EE to version 16.9.7, 16.10.5, 16.11.2 or later. Alternatively, ensure no banned users remain in groups with access to sensitive issues.
16.11.2
- Identify your current GitLab version from the affected version ranges (15.2.0 to 16.9.6, 16.10.0 to 16.10.4, or 16.11.0 to 16.11.1)
- Upgrade GitLab to version 16.9.7, 16.10.5, or 16.11.2 (or later) depending on your current branch
- After upgrade, verify the patch was applied by checking GitLab version information
- Confirm that banned group members can no longer view issue updates via the API
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-2024-1539 — 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-2024-1539 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