What is the severity of CVE-2022-0344?

CVE-2022-0344 is classified as a medium severity vulnerability.

How do I fix CVE-2022-0344?

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

What are the potential impacts of CVE-2022-0344?

The potential impact of CVE-2022-0344 is the unauthorized disclosure of private project paths.

Who is affected by CVE-2022-0344?

CVE-2022-0344 affects all versions of GitLab starting from 10.0 before 14.5.4, 10.1 before 14.6.4, and 10.2 before 14.7.1.

How does the vulnerability CVE-2022-0344 occur?

CVE-2022-0344 occurs when an issue is closed via a merge request, allowing system notes to expose private project paths.

Vulnerability/
CVE-2022-0344

medium

4.3

28/3/2022

2/8/2024

CVE-2022-0344

First published: Mon Mar 28 2022(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 10.0 before 14.5.4, all versions starting from 10.1 before 14.6.4, all versions starting from 10.2 before 14.7.1. Private project paths can be disclosed to unauthorized users via system notes when an Issue is closed via a Merge Request and later moved to a public project

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.0<14.5.4
GitLab	>=14.6.0<14.6.4
GitLab	=14.7.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0344?
CVE-2022-0344 is classified as a medium severity vulnerability.
How do I fix CVE-2022-0344?
To fix CVE-2022-0344, upgrade to GitLab version 14.5.4, 14.6.4, or 14.7.1 or later.
What are the potential impacts of CVE-2022-0344?
The potential impact of CVE-2022-0344 is the unauthorized disclosure of private project paths.
Who is affected by CVE-2022-0344?
CVE-2022-0344 affects all versions of GitLab starting from 10.0 before 14.5.4, 10.1 before 14.6.4, and 10.2 before 14.7.1.
How does the vulnerability CVE-2022-0344 occur?
CVE-2022-0344 occurs when an issue is closed via a merge request, allowing system notes to expose private project paths.

agent/type
agent/references
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.6.0
version/gitlab/14.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-0344?
CVE-2022-0344 is classified as a medium severity vulnerability.
How do I fix CVE-2022-0344?
To fix CVE-2022-0344, upgrade to GitLab version 14.5.4, 14.6.4, or 14.7.1 or later.
What are the potential impacts of CVE-2022-0344?
The potential impact of CVE-2022-0344 is the unauthorized disclosure of private project paths.
Who is affected by CVE-2022-0344?
CVE-2022-0344 affects all versions of GitLab starting from 10.0 before 14.5.4, 10.1 before 14.6.4, and 10.2 before 14.7.1.
How does the vulnerability CVE-2022-0344 occur?
CVE-2022-0344 occurs when an issue is closed via a merge request, allowing system notes to expose private project paths.