GitLabApplication
CVE-2023-5831
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 CE/EE affecting all versions starting from 16.0 before 16.3.6, all versions starting from 16.4 before 16.4.2, and all versions starting from 16.5.0 before 16.5.1 which have the `super_sidebar_logged_out` feature flag enabled. Affected versions with this default-disabled feature flag enabled may unintentionally disclose GitLab version metadata to unauthorized actors.
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 feature flag named `super_sidebar_logged_out` in GitLab CE/EE versions 16.0 through 16.5.1, when enabled, causes the application to disclose GitLab version metadata to unauthenticated/unauthorized users. This information disclosure could aid attackers in identifying vulnerable targets.
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
>= 16.0.0, < 16.3.6>= 16.4.0, < 16.4.2= 16.5.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
- 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:version` or check the Admin Area > Help page for the version numberAffected if Version is 16.0.0 through 16.5.1 (specifically >= 16.0.0 and < 16.3.6, OR >= 16.4.0 and < 16.4.2, OR = 16.5.0)
-
Verify super_sidebar_logged_out feature flag statusAccess GitLab Rails console and run: `Feature.enabled?(:super_sidebar_logged_out)` OR check in Admin Area under Settings > Feature FlagsAffected if The feature flag is set to enabled (true)
You are affected if your GitLab version falls within 16.0.0-16.5.1 (per the specific ranges) AND the super_sidebar_logged_out feature flag is enabled, as this configuration exposes version metadata to unauthenticated 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.
dbcve · scoped16.3.616.4.2
Disable the `super_sidebar_logged_out` feature flag if enabled, or upgrade to GitLab versions 16.3.6, 16.4.2, 16.5.1 or later which contain the fix.
16.3.6, 16.4.2, or 16.5.1 (or later stable release)
- Check if the `super_sidebar_logged_out` feature flag is enabled in your GitLab instance (typically found in GitLab Rails console or admin settings)
- If the feature flag is enabled, either disable it as a temporary mitigation, or upgrade to a fixed release
- If upgrading, select a version >= 16.3.6, >= 16.4.2, or >= 16.5.1 based on your current major version branch
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5831 — 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-2023-5831 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