What is the severity of CVE-2019-15734?

The severity of CVE-2019-15734 is classified as medium due to unauthorized access to certain commit titles and comments under specific conditions.

Who is affected by CVE-2019-15734?

CVE-2019-15734 affects users of GitLab Community and Enterprise Editions versions 8.6 through 12.2.1.

How do I fix CVE-2019-15734?

To fix CVE-2019-15734, update your GitLab installation to version 12.2.3 or later.

What are the potential impacts of CVE-2019-15734?

The potential impacts of CVE-2019-15734 include unauthorized visibility of commit titles and team member comments.

Is there a workaround for CVE-2019-15734?

There are no specific workarounds for CVE-2019-15734; upgrading is the recommended action.

Vulnerability/
CVE-2019-15734

medium

4.3

CWE

200

16/9/2019

5/8/2024

CVE-2019-15734: Infoleak

First published: Mon Sep 16 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 8.6 through 12.2.1. Under very specific conditions, commit titles and team member comments could become viewable to users who did not have permission to access these.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.6.0<12.0.8
GitLab	>=8.6.0<12.0.8
GitLab	>=12.1.0<12.1.8
GitLab	>=12.1.0<12.1.8
GitLab	>=12.2.0<12.2.3
GitLab	>=12.2.0<12.2.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-15734?
The severity of CVE-2019-15734 is classified as medium due to unauthorized access to certain commit titles and comments under specific conditions.
Who is affected by CVE-2019-15734?
CVE-2019-15734 affects users of GitLab Community and Enterprise Editions versions 8.6 through 12.2.1.
How do I fix CVE-2019-15734?
To fix CVE-2019-15734, update your GitLab installation to version 12.2.3 or later.
What are the potential impacts of CVE-2019-15734?
The potential impacts of CVE-2019-15734 include unauthorized visibility of commit titles and team member comments.
Is there a workaround for CVE-2019-15734?
There are no specific workarounds for CVE-2019-15734; upgrading is the recommended action.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
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/8.6.0
version/gitlab/12.1.0
version/gitlab/12.2.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-2019-15734?
The severity of CVE-2019-15734 is classified as medium due to unauthorized access to certain commit titles and comments under specific conditions.
Who is affected by CVE-2019-15734?
CVE-2019-15734 affects users of GitLab Community and Enterprise Editions versions 8.6 through 12.2.1.
How do I fix CVE-2019-15734?
To fix CVE-2019-15734, update your GitLab installation to version 12.2.3 or later.
What are the potential impacts of CVE-2019-15734?
The potential impacts of CVE-2019-15734 include unauthorized visibility of commit titles and team member comments.
Is there a workaround for CVE-2019-15734?
There are no specific workarounds for CVE-2019-15734; upgrading is the recommended action.