What is the severity of CVE-2022-2095?

CVE-2022-2095 has a medium severity due to improper access control allowing unauthorized information disclosure.

How do I fix CVE-2022-2095?

To fix CVE-2022-2095, upgrade GitLab to version 15.0.5 or later, 15.1.4 or later, or 15.2.1 or later.

Which versions of GitLab are affected by CVE-2022-2095?

CVE-2022-2095 affects all versions of GitLab CE/EE starting from 13.7 before 15.0.5 and from 15.1 before 15.1.4, and from 15.2 before 15.2.1.

What type of vulnerability is CVE-2022-2095?

CVE-2022-2095 is classified as an improper access control vulnerability.

Can a non-authenticated user exploit CVE-2022-2095?

No, CVE-2022-2095 can only be exploited by a malicious authenticated user.

Vulnerability/
CVE-2022-2095

medium

4.3

CWE

863

5/8/2022

3/8/2024

CVE-2022-2095

First published: Fri Aug 05 2022(Updated: )

An improper access control check in GitLab CE/EE affecting all versions starting from 13.7 before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1 allows a malicious authenticated user to view a public project's Deploy Key's public fingerprint and name when that key has write permission. Note that GitLab never asks for nor stores the private key.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.7.0<15.0.5
GitLab	>=15.1.0<15.1.4
GitLab	=15.2
GitLab	>=13.7.0<15.0.5
GitLab	>=15.1.0<15.1.4
GitLab	=15.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2095?
CVE-2022-2095 has a medium severity due to improper access control allowing unauthorized information disclosure.
How do I fix CVE-2022-2095?
To fix CVE-2022-2095, upgrade GitLab to version 15.0.5 or later, 15.1.4 or later, or 15.2.1 or later.
Which versions of GitLab are affected by CVE-2022-2095?
CVE-2022-2095 affects all versions of GitLab CE/EE starting from 13.7 before 15.0.5 and from 15.1 before 15.1.4, and from 15.2 before 15.2.1.
What type of vulnerability is CVE-2022-2095?
CVE-2022-2095 is classified as an improper access control vulnerability.
Can a non-authenticated user exploit CVE-2022-2095?
No, CVE-2022-2095 can only be exploited by a malicious authenticated user.

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/13.7.0
version/gitlab/15.1.0
version/gitlab/15.2

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-2095?
CVE-2022-2095 has a medium severity due to improper access control allowing unauthorized information disclosure.
How do I fix CVE-2022-2095?
To fix CVE-2022-2095, upgrade GitLab to version 15.0.5 or later, 15.1.4 or later, or 15.2.1 or later.
Which versions of GitLab are affected by CVE-2022-2095?
CVE-2022-2095 affects all versions of GitLab CE/EE starting from 13.7 before 15.0.5 and from 15.1 before 15.1.4, and from 15.2 before 15.2.1.
What type of vulnerability is CVE-2022-2095?
CVE-2022-2095 is classified as an improper access control vulnerability.
Can a non-authenticated user exploit CVE-2022-2095?
No, CVE-2022-2095 can only be exploited by a malicious authenticated user.