What is the severity of CVE-2022-4037?

CVE-2022-4037 has been classified with a high severity due to its potential for verified email forgery and third-party account takeover.

How do I fix CVE-2022-4037?

To fix CVE-2022-4037, update GitLab to version 15.5.7, 15.6.4, or 15.7.2 or later.

What versions of GitLab are affected by CVE-2022-4037?

CVE-2022-4037 affects all versions of GitLab before 15.5.7 and all versions starting from 15.6 up to 15.6.4 and from 15.7 up to 15.7.2.

What type of vulnerability is CVE-2022-4037?

CVE-2022-4037 is a race condition vulnerability that can lead to account takeover.

What impact does CVE-2022-4037 have on users?

The impact of CVE-2022-4037 includes the possibility of unauthorized access to user accounts through email forgery.

Vulnerability/
CVE-2022-4037

high

8.5

CWE

362

12/1/2023

3/8/2024

CVE-2022-4037: Race Condition

First published: Thu Jan 12 2023(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions before 15.5.7, all versions starting from 15.6 before 15.6.4, all versions starting from 15.7 before 15.7.2. A race condition can lead to verified email forgery and takeover of third-party accounts when using GitLab as an OAuth provider.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<15.5.7
GitLab	<15.5.7
GitLab	>=15.6.0<15.6.4
GitLab	>=15.6.0<15.6.4
GitLab	>=15.7.0<15.7.2
GitLab	>=15.7.0<15.7.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-4037?
CVE-2022-4037 has been classified with a high severity due to its potential for verified email forgery and third-party account takeover.
How do I fix CVE-2022-4037?
To fix CVE-2022-4037, update GitLab to version 15.5.7, 15.6.4, or 15.7.2 or later.
What versions of GitLab are affected by CVE-2022-4037?
CVE-2022-4037 affects all versions of GitLab before 15.5.7 and all versions starting from 15.6 up to 15.6.4 and from 15.7 up to 15.7.2.
What type of vulnerability is CVE-2022-4037?
CVE-2022-4037 is a race condition vulnerability that can lead to account takeover.
What impact does CVE-2022-4037 have on users?
The impact of CVE-2022-4037 includes the possibility of unauthorized access to user accounts through email forgery.

agent/type
agent/references
agent/author
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/15.6.0
version/gitlab/15.7.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-4037?
CVE-2022-4037 has been classified with a high severity due to its potential for verified email forgery and third-party account takeover.
How do I fix CVE-2022-4037?
To fix CVE-2022-4037, update GitLab to version 15.5.7, 15.6.4, or 15.7.2 or later.
What versions of GitLab are affected by CVE-2022-4037?
CVE-2022-4037 affects all versions of GitLab before 15.5.7 and all versions starting from 15.6 up to 15.6.4 and from 15.7 up to 15.7.2.
What type of vulnerability is CVE-2022-4037?
CVE-2022-4037 is a race condition vulnerability that can lead to account takeover.
What impact does CVE-2022-4037 have on users?
The impact of CVE-2022-4037 includes the possibility of unauthorized access to user accounts through email forgery.