CVE-2023-2233Public exploitNetwork attack vector

Sentry project disclosure via owner-only endpoint bypass

Published Sep 29, 2023 · Updated Nov 20, 2025

Improper authorization in GitLab 11.8 through 16.2.7, 16.3.0 through 16.3.4, and 16.4.0 allows remote authenticated users to list Sentry projects. The -/error_tracking/projects endpoint accepts an attacker-supplied Sentry API host and fetches its project list without enforcing the owner-only authorization required by the settings interface. Reporter access to the GitLab project, an enabled Sentry integration, and knowledge of its domain are required; exposure is limited to Sentry project identifiers and names.

CVSS severity3.1
Low
EPSS probability0.45%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authorization in GitLab 11.8 through 16.2.7, 16.3.0 through 16.3.4, and 16.4.0 allows remote authenticated users to list Sentry projects. The -/error_tracking/projects endpoint accepts an attacker-supplied Sentry API host and fetches its project list without enforcing the owner-only authorization required by the settings interface. Reporter access to the GitLab project, an enabled Sentry integration, and knowledge of its domain are required; exposure is limited to Sentry project identifiers and names.

The record

CVE
CVE-2023-2233
Published
Sep 29, 2023
Updated
Nov 20, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-862, T1213
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 29, 2023CVE publishedPublication date reported by the CVE source.
  2. Nov 20, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=11.8 <16.2.8
  2. Affected versionversion=16.3 <16.3.5
  3. Affected versionversion=16.4 <16.4.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=11.8 <16.2.8; version=16.3 <16.3.5; version=16.4 <16.4.1

Published CVSS scores

3.1GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-862Missing Authorization
T1213Data from Information Repositories

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo