GitLabApplication
CVE-2023-1167
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 · uneditedImproper authorization in Gitlab EE affecting all versions from 12.3.0 before 15.8.5, all versions starting from 15.9 before 15.9.4, all versions starting from 15.10 before 15.10.1 allows an unauthorized access to security reports in MR.
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 confidenceImproper authorization vulnerability in GitLab Enterprise Edition allows unauthorized users to access security reports within merge requests. This occurs due to insufficient access control checks on security report endpoints, enabling attackers to view sensitive vulnerability information they should not have permission to access.
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
>= 12.3.0, < 15.8.5>= 15.9.0, < 15.9.4= 15.10.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 `sudo gitlab-rake gitlab:version` or check `/opt/gitlab/VERSION` file to determine the exact GitLab version installedAffected if Version falls within >= 12.3.0 and < 15.8.5, OR >= 15.9.0 and < 15.9.4, OR equals 15.10.0
-
Verify merge request security reports are enabledCheck if projects have merge requests with integrated security scanning (Dependency Scanning, SAST, or similar) enabled in CI/CD pipeline configurationAffected if Security report features are active and the GitLab version is vulnerable
-
Confirm security report endpoint accessibilityAs an unauthorized user, attempt to access a security report endpoint for a merge request in a private project where you lack reporter or developer permissions (e.g., navigate to merge request security tab or API endpoint for security report)Affected if User can view security vulnerability details without having the required role on the project
If the installed GitLab version is within the affected ranges and merge requests with security reports exist, the environment is vulnerable to unauthorized access of sensitive security findings.
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 · scoped15.8.515.9.4
Upgrade GitLab to version 15.8.5, 15.9.4, 15.10.1 or later. Apply the appropriate patch in a staging environment first to verify compatibility before production deployment.
15.8.5, 15.9.4, or 15.10.1 (or later stable releases)
- Back up your GitLab instance data and configuration before upgrading
- Review GitLab's upgrade path documentation to ensure compatibility with your current version
- Upgrade to GitLab 15.8.5, 15.9.4, or 15.10.1 (or a later stable version in your respective branch)
- After upgrade, verify that the GitLab instance is running correctly
- Confirm that authorization controls for security reports in merge requests are working properly
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-2023-1167 — 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-1167 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