What is the severity of CVE-2022-1193?

CVE-2022-1193 is categorized as a high severity vulnerability due to its potential for unauthorized access to project details.

How do I fix CVE-2022-1193?

To fix CVE-2022-1193, you should upgrade GitLab CE/EE to versions 14.7.7, 14.8.5, or 14.9.2 or later.

What types of projects are affected by CVE-2022-1193?

CVE-2022-1193 affects private projects in GitLab where improper access controls allow unauthorized information exposure.

Can CVE-2022-1193 be exploited remotely?

Yes, CVE-2022-1193 can be exploited remotely by a malicious actor under specific conditions.

What versions of GitLab are vulnerable to CVE-2022-1193?

Vulnerable versions of GitLab include all versions from 10.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2.

Vulnerability/
CVE-2022-1193

medium

4.3

CWE

863

11/4/2022

2/8/2024

CVE-2022-1193

First published: Mon Apr 11 2022(Updated: )

Improper access control in GitLab CE/EE versions 10.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allows a malicious actor to obtain details of the latest commit in a private project via Merge Requests under certain circumstances

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.7.0<14.7.7
GitLab	>=10.7.0<14.7.7
GitLab	>=14.8.0<14.8.5
GitLab	>=14.8.0<14.8.5
GitLab	>=14.9.0<14.9.2
GitLab	>=14.9.0<14.9.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1193?
CVE-2022-1193 is categorized as a high severity vulnerability due to its potential for unauthorized access to project details.
How do I fix CVE-2022-1193?
To fix CVE-2022-1193, you should upgrade GitLab CE/EE to versions 14.7.7, 14.8.5, or 14.9.2 or later.
What types of projects are affected by CVE-2022-1193?
CVE-2022-1193 affects private projects in GitLab where improper access controls allow unauthorized information exposure.
Can CVE-2022-1193 be exploited remotely?
Yes, CVE-2022-1193 can be exploited remotely by a malicious actor under specific conditions.
What versions of GitLab are vulnerable to CVE-2022-1193?
Vulnerable versions of GitLab include all versions from 10.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/10.7.0
version/gitlab/14.8.0
version/gitlab/14.9.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-1193?
CVE-2022-1193 is categorized as a high severity vulnerability due to its potential for unauthorized access to project details.
How do I fix CVE-2022-1193?
To fix CVE-2022-1193, you should upgrade GitLab CE/EE to versions 14.7.7, 14.8.5, or 14.9.2 or later.
What types of projects are affected by CVE-2022-1193?
CVE-2022-1193 affects private projects in GitLab where improper access controls allow unauthorized information exposure.
Can CVE-2022-1193 be exploited remotely?
Yes, CVE-2022-1193 can be exploited remotely by a malicious actor under specific conditions.
What versions of GitLab are vulnerable to CVE-2022-1193?
Vulnerable versions of GitLab include all versions from 10.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2.