What is CVE-2022-4343?

CVE-2022-4343 is an issue discovered in GitLab EE that can potentially allow a project member to leak stored credentials.

Which versions of GitLab EE are affected by CVE-2022-4343?

Versions starting from 13.12 before 16.1.5, versions starting from 16.2 before 16.2.5, and version 16.3 before 16.3.1 of GitLab EE are affected by CVE-2022-4343.

What is the severity of CVE-2022-4343?

The severity of CVE-2022-4343 is medium with a severity value of 4.3.

How can a project member leak credentials in GitLab EE due to CVE-2022-4343?

A project member can leak credentials stored in the site profile due to the vulnerability in GitLab EE.

How can I fix CVE-2022-4343 in GitLab EE?

To fix CVE-2022-4343 in GitLab EE, you should update to version 16.1.5, 16.2.5, or 16.3.1 or later.

Vulnerability/
CVE-2022-4343

medium

CWE

200

1/9/2023

18/9/2024

CVE-2022-4343: Exposure of Sensitive Information to an Unauthorized Actor in GitLab

First published: Fri Sep 01 2023(Updated: )

An issue has been discovered in GitLab EE affecting all versions starting from 13.12 before 16.1.5, all versions starting from 16.2 before 16.2.5, all versions starting from 16.3 before 16.3.1 in which a project member can leak credentials stored in site profile.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab GitLab	>=13.12<16.1.5
GitLab GitLab	>=16.2<16.2.5
GitLab GitLab	=16.3.0

Remedy

Upgrade to versions 16.1.5, 16.2.5, 16.3.1 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is CVE-2022-4343?
CVE-2022-4343 is an issue discovered in GitLab EE that can potentially allow a project member to leak stored credentials.
Which versions of GitLab EE are affected by CVE-2022-4343?
Versions starting from 13.12 before 16.1.5, versions starting from 16.2 before 16.2.5, and version 16.3 before 16.3.1 of GitLab EE are affected by CVE-2022-4343.
What is the severity of CVE-2022-4343?
The severity of CVE-2022-4343 is medium with a severity value of 4.3.
How can a project member leak credentials in GitLab EE due to CVE-2022-4343?
A project member can leak credentials stored in the site profile due to the vulnerability in GitLab EE.
How can I fix CVE-2022-4343 in GitLab EE?
To fix CVE-2022-4343 in GitLab EE, you should update to version 16.1.5, 16.2.5, or 16.3.1 or later.

agent/author
agent/references
agent/type
collector/nvd-api
agent/software-canonical-lookup-request
collector/nvd-index
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/title
agent/last-modified-date
agent/remedy
agent/first-publish-date
agent/tags
agent/event
vendor/gitlab
canonical/gitlab gitlab
version/gitlab gitlab/13.12
version/gitlab gitlab/16.2
version/gitlab gitlab/16.3.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.