What is the severity of CVE-2022-0371?

CVE-2022-0371 is classified as a high severity vulnerability.

How do I fix CVE-2022-0371?

To fix CVE-2022-0371, upgrade GitLab to version 14.5.4 or later, 14.6.4 or later, or 14.7.1 or later.

Who is affected by CVE-2022-0371?

CVE-2022-0371 affects all versions of GitLab CE/EE from 11.4 up to but not including 14.5.4, 14.6 up to but not including 14.6.4, and 14.7 up to but not including 14.7.1.

What type of vulnerability is CVE-2022-0371?

CVE-2022-0371 is considered a data exposure vulnerability that allows authenticated users to search for other users' private emails.

Is there a workaround for CVE-2022-0371?

There is no documented workaround for CVE-2022-0371; updating to a fixed version is the recommended action.

Vulnerability/
CVE-2022-0371

medium

4.3

28/3/2022

2/8/2024

CVE-2022-0371

First published: Mon Mar 28 2022(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.4 before 14.5.4, all versions starting from 14.6 before 14.6.4, all versions starting from 14.7 before 14.7.1. GitLab search may allow authenticated users to search other users by their respective private emails even if a user set their email to private.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=11.4<14.5.4
GitLab	>=11.4<14.5.4
GitLab	>=14.6<14.6.4
GitLab	>=14.6<14.6.4
GitLab	>=14.7<14.7.1
GitLab	>=14.7<14.7.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0371?
CVE-2022-0371 is classified as a high severity vulnerability.
How do I fix CVE-2022-0371?
To fix CVE-2022-0371, upgrade GitLab to version 14.5.4 or later, 14.6.4 or later, or 14.7.1 or later.
Who is affected by CVE-2022-0371?
CVE-2022-0371 affects all versions of GitLab CE/EE from 11.4 up to but not including 14.5.4, 14.6 up to but not including 14.6.4, and 14.7 up to but not including 14.7.1.
What type of vulnerability is CVE-2022-0371?
CVE-2022-0371 is considered a data exposure vulnerability that allows authenticated users to search for other users' private emails.
Is there a workaround for CVE-2022-0371?
There is no documented workaround for CVE-2022-0371; updating to a fixed version is the recommended action.

agent/references
agent/type
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/11.4
version/gitlab/14.6
version/gitlab/14.7

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-0371?
CVE-2022-0371 is classified as a high severity vulnerability.
How do I fix CVE-2022-0371?
To fix CVE-2022-0371, upgrade GitLab to version 14.5.4 or later, 14.6.4 or later, or 14.7.1 or later.
Who is affected by CVE-2022-0371?
CVE-2022-0371 affects all versions of GitLab CE/EE from 11.4 up to but not including 14.5.4, 14.6 up to but not including 14.6.4, and 14.7 up to but not including 14.7.1.
What type of vulnerability is CVE-2022-0371?
CVE-2022-0371 is considered a data exposure vulnerability that allows authenticated users to search for other users' private emails.
Is there a workaround for CVE-2022-0371?
There is no documented workaround for CVE-2022-0371; updating to a fixed version is the recommended action.