What is the severity of CVE-2022-4255?

CVE-2022-4255 has been classified as a medium severity vulnerability due to the potential exposure of user email addresses.

How do I fix CVE-2022-4255?

To fix CVE-2022-4255, upgrade GitLab to version 15.4.6, 15.5.5, or 15.6.1 or later.

What kind of information is leaked in CVE-2022-4255?

CVE-2022-4255 exposes user email addresses through webhook payloads.

Is CVE-2022-4255 specific to any GitLab edition?

CVE-2022-4255 affects both the community and enterprise editions of GitLab.

Vulnerability/
CVE-2022-4255

medium

5.3

27/1/2023

3/8/2024

CVE-2022-4255

Q: What versions are affected by CVE-2022-4255?

CVE-2022-4255 affects all versions of GitLab EE from 13.7 prior to 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1.

First published: Fri Jan 27 2023(Updated: )

An info leak issue was identified in all versions of GitLab EE from 13.7 prior to 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1 which exposes user email id through webhook payload.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.7.0<15.4.6
GitLab	>=13.7.0<15.4.6
GitLab	>=15.5.0<15.5.5
GitLab	>=15.5.0<15.5.5
GitLab	=15.6.0
GitLab	=15.6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-4255?
CVE-2022-4255 has been classified as a medium severity vulnerability due to the potential exposure of user email addresses.
How do I fix CVE-2022-4255?
To fix CVE-2022-4255, upgrade GitLab to version 15.4.6, 15.5.5, or 15.6.1 or later.
What versions are affected by CVE-2022-4255?
CVE-2022-4255 affects all versions of GitLab EE from 13.7 prior to 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1.
What kind of information is leaked in CVE-2022-4255?
CVE-2022-4255 exposes user email addresses through webhook payloads.
Is CVE-2022-4255 specific to any GitLab edition?
CVE-2022-4255 affects both the community and enterprise editions of GitLab.

agent/references
agent/type
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.7.0
version/gitlab/15.5.0
version/gitlab/15.6.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-4255?
CVE-2022-4255 has been classified as a medium severity vulnerability due to the potential exposure of user email addresses.
How do I fix CVE-2022-4255?
To fix CVE-2022-4255, upgrade GitLab to version 15.4.6, 15.5.5, or 15.6.1 or later.
What versions are affected by CVE-2022-4255?
CVE-2022-4255 affects all versions of GitLab EE from 13.7 prior to 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1.
What kind of information is leaked in CVE-2022-4255?
CVE-2022-4255 exposes user email addresses through webhook payloads.
Is CVE-2022-4255 specific to any GitLab edition?
CVE-2022-4255 affects both the community and enterprise editions of GitLab.