What is the severity of CVE-2022-2243?

CVE-2022-2243 is considered a moderate severity vulnerability as it allows authenticated users to enumerate issues in non-linked sentry projects.

How do I fix CVE-2022-2243?

To fix CVE-2022-2243, update your GitLab instance to version 14.10.5 or later, 15.0.4 or later, or 15.1.1 or later.

What versions are affected by CVE-2022-2243?

CVE-2022-2243 affects GitLab versions 14.8 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.

Who can exploit CVE-2022-2243?

CVE-2022-2243 can be exploited by any authenticated user within GitLab.

What type of vulnerability is CVE-2022-2243?

CVE-2022-2243 is classified as an access control vulnerability.

Vulnerability/
CVE-2022-2243

medium

CWE

639

1/7/2022

3/8/2024

CVE-2022-2243

First published: Fri Jul 01 2022(Updated: )

An access control vulnerability in GitLab EE/CE affecting all versions from 14.8 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1, allows authenticated users to enumerate issues in non-linked sentry projects.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=14.8.0<14.10.5
GitLab	>=14.8.0<14.10.5
GitLab	>=15.0.0<15.0.4
GitLab	>=15.0.0<15.0.4
GitLab	=15.1.0
GitLab	=15.1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2243?
CVE-2022-2243 is considered a moderate severity vulnerability as it allows authenticated users to enumerate issues in non-linked sentry projects.
How do I fix CVE-2022-2243?
To fix CVE-2022-2243, update your GitLab instance to version 14.10.5 or later, 15.0.4 or later, or 15.1.1 or later.
What versions are affected by CVE-2022-2243?
CVE-2022-2243 affects GitLab versions 14.8 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.
Who can exploit CVE-2022-2243?
CVE-2022-2243 can be exploited by any authenticated user within GitLab.
What type of vulnerability is CVE-2022-2243?
CVE-2022-2243 is classified as an access control vulnerability.

agent/author
agent/type
agent/references
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
collector/nvd-api
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/14.8.0
version/gitlab/15.0.0
version/gitlab/15.1.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-2243?
CVE-2022-2243 is considered a moderate severity vulnerability as it allows authenticated users to enumerate issues in non-linked sentry projects.
How do I fix CVE-2022-2243?
To fix CVE-2022-2243, update your GitLab instance to version 14.10.5 or later, 15.0.4 or later, or 15.1.1 or later.
What versions are affected by CVE-2022-2243?
CVE-2022-2243 affects GitLab versions 14.8 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.
Who can exploit CVE-2022-2243?
CVE-2022-2243 can be exploited by any authenticated user within GitLab.
What type of vulnerability is CVE-2022-2243?
CVE-2022-2243 is classified as an access control vulnerability.