What is the severity of CVE-2022-0738?

CVE-2022-0738 has been rated as a medium severity vulnerability.

How do I fix CVE-2022-0738?

To fix CVE-2022-0738, upgrade GitLab to version 14.6.5, 14.7.4, or 14.8.2 or later.

What systems are affected by CVE-2022-0738?

CVE-2022-0738 affects all GitLab versions starting from 14.6 before 14.6.5, 14.7 before 14.7.4, and 14.8 before 14.8.2.

Are both GitLab Community and Enterprise affected by CVE-2022-0738?

Yes, both GitLab Community and Enterprise editions are affected by CVE-2022-0738.

Vulnerability/
CVE-2022-0738

high

7.5

CWE

522

28/3/2022

2/8/2024

CVE-2022-0738

Q: What type of information was leaked in CVE-2022-0738?

CVE-2022-0738 involved the leaking of user passwords when adding mirrors with SSH credentials under specific conditions.

First published: Mon Mar 28 2022(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 14.6 before 14.6.5, all versions starting from 14.7 before 14.7.4, all versions starting from 14.8 before 14.8.2. GitLab was leaking user passwords when adding mirrors with SSH credentials under specific conditions.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.0<14.6.5
GitLab	>=10.0<14.6.5
GitLab	>=14.7<14.7.4
GitLab	>=14.7<14.7.4
GitLab	>=14.8<14.8.2
GitLab	>=14.8<14.8.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0738?
CVE-2022-0738 has been rated as a medium severity vulnerability.
How do I fix CVE-2022-0738?
To fix CVE-2022-0738, upgrade GitLab to version 14.6.5, 14.7.4, or 14.8.2 or later.
What systems are affected by CVE-2022-0738?
CVE-2022-0738 affects all GitLab versions starting from 14.6 before 14.6.5, 14.7 before 14.7.4, and 14.8 before 14.8.2.
What type of information was leaked in CVE-2022-0738?
CVE-2022-0738 involved the leaking of user passwords when adding mirrors with SSH credentials under specific conditions.
Are both GitLab Community and Enterprise affected by CVE-2022-0738?
Yes, both GitLab Community and Enterprise editions are affected by CVE-2022-0738.

agent/references
agent/type
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.0
version/gitlab/14.7
version/gitlab/14.8

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-0738?
CVE-2022-0738 has been rated as a medium severity vulnerability.
How do I fix CVE-2022-0738?
To fix CVE-2022-0738, upgrade GitLab to version 14.6.5, 14.7.4, or 14.8.2 or later.
What systems are affected by CVE-2022-0738?
CVE-2022-0738 affects all GitLab versions starting from 14.6 before 14.6.5, 14.7 before 14.7.4, and 14.8 before 14.8.2.
What type of information was leaked in CVE-2022-0738?
CVE-2022-0738 involved the leaking of user passwords when adding mirrors with SSH credentials under specific conditions.
Are both GitLab Community and Enterprise affected by CVE-2022-0738?
Yes, both GitLab Community and Enterprise editions are affected by CVE-2022-0738.