CVE-2022-2243Network attack vector

Authenticated issue disclosure via unchecked Sentry project binding

Published Jul 1, 2022 · Updated Aug 3, 2024

Improper access control in GitLab 14.8 through 14.10.4, 15.0 through 15.0.3, and 15.1.0 allows remote authenticated users to read Sentry issues. The Sentry error-tracking issue lookup accepts an attacker-controlled issue identifier and retrieves an issue without verifying that its Sentry project is linked to the current GitLab project. A valid GitLab account is required, and exposure is limited to issue data from other Sentry projects available through the configured Sentry integration.

CVSS severity5.0
Medium
EPSS probability0.75%
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 access control in GitLab 14.8 through 14.10.4, 15.0 through 15.0.3, and 15.1.0 allows remote authenticated users to read Sentry issues. The Sentry error-tracking issue lookup accepts an attacker-controlled issue identifier and retrieves an issue without verifying that its Sentry project is linked to the current GitLab project. A valid GitLab account is required, and exposure is limited to issue data from other Sentry projects available through the configured Sentry integration.

The record

CVE
CVE-2022-2243
Published
Jul 1, 2022
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-639, T1213
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 1, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record 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=>=14.8, <14.10.5
  2. Affected versionversion=>=15.0, <15.0.4
  3. Affected versionversion=>=15.1, <15.1.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=14.8, <14.10.5; version=>=15.0, <15.0.4; version=>=15.1, <15.1.1

Published CVSS scores

4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
5.0GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
4.0NIST NVDAV:N/AC:L/Au:S/C:P/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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
T1213Data from Information Repositories

Public exploit references

No public exploit references are available in this record.

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