GitLabApplication
CVE-2023-1710
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 · uneditedA sensitive information disclosure vulnerability in GitLab affecting all versions from 15.0 prior to 15.8.5, 15.9 prior to 15.9.4 and 15.10 prior to 15.10.1 allows an attacker to view the count of internal notes for a given 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 confidenceThis GitLab vulnerability allows attackers to view the count of internal (confidential) notes on issues through improper API access controls. Internal notes are typically used for sensitive discussions not visible to regular users, and revealing their existence/count provides reconnaissance value to attackers.
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.0.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.
-
Determine installed GitLab versionRun `sudo gitlab-rake gitlab:version` or check the /opt/gitlab/version fileAffected if The version falls within >= 15.0.0 and < 15.8.5, OR >= 15.9.0 and < 15.9.4, OR equals 15.10.0
-
Verify internal notes feature is in useCheck if any projects have issues with confidential notes created by clicking the 'Make confidential' option when adding a noteAffected if Confidential/internal notes exist on any issue in the GitLab instance
-
Check API endpoint access controlsAttempt a GET request to the notes API endpoint for a confidential issue using a low-privilege or unauthenticated user account to see if note count is returnedAffected if The API returns the count of internal notes to unauthorized users without returning the actual note content
-
Review API access logsInspect GitLab API access logs for requests to note-related endpoints that return note counts for confidential issues from non-authorized usersAffected if Unprivileged users are successfully querying note counts on internal issues
You are affected if your GitLab version is 15.0.0 through 15.8.4, 15.9.0 through 15.9.3, or exactly 15.10.0 AND you have confidential/internal notes on issues accessible to unprivileged 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 · scoped15.8.515.9.4
Upgrade GitLab to version 15.8.5, 15.9.4, or 15.10.1 or later to patch the access control flaw that allows unauthorized viewing of internal note counts.
Upgrade to GitLab 15.8.5, 15.9.4, or 15.10.1 (or later) depending on your current version branch
- 1. Back up your GitLab instance data and configuration
- 2. Identify your current GitLab version using the GitLab admin panel or `gitlab-rake gitlab:env:info`
- 3. If running >= 15.0.0 and < 15.8.5: plan upgrade to 15.8.5 or later 15.8.x release
- 4. If running >= 15.9.0 and < 15.9.4: plan upgrade to 15.9.4
- 5. If running 15.10.0: plan upgrade to 15.10.1
- 6. Review GitLab upgrade prerequisites and ensure compatible underlying infrastructure (Ruby, PostgreSQL, etc.)
- 7. Execute upgrade following GitLab's standard upgrade documentation for your deployment method (omnibus, source, etc.)
- 8. Verify upgrade completed successfully and GitLab is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1710 — 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-1710 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