What is the severity of CVE-2019-15741?

CVE-2019-15741 is classified as a medium severity vulnerability that can lead to privilege escalation.

How do I fix CVE-2019-15741?

To fix CVE-2019-15741, you should upgrade your GitLab Omnibus installation to version 12.2.3 or later.

Which versions of GitLab Omnibus are affected by CVE-2019-15741?

CVE-2019-15741 affects GitLab Omnibus versions from 7.4.0 to 12.2.1.

What consequences could result from exploiting CVE-2019-15741?

Exploitation of CVE-2019-15741 could allow an unauthorized user to gain elevated privileges on the affected system.

Is there a workaround for CVE-2019-15741?

Currently, there is no known workaround for CVE-2019-15741; upgrading is the recommended action.

Vulnerability/
CVE-2019-15741

critical

9.8

16/9/2019

5/8/2024

CVE-2019-15741

First published: Mon Sep 16 2019(Updated: )

An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. An unsafe interaction with logrotate could result in a privilege escalation

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=7.4.0<12.0.8
GitLab	>=12.1.0<12.1.8
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-15741?
CVE-2019-15741 is classified as a medium severity vulnerability that can lead to privilege escalation.
How do I fix CVE-2019-15741?
To fix CVE-2019-15741, you should upgrade your GitLab Omnibus installation to version 12.2.3 or later.
Which versions of GitLab Omnibus are affected by CVE-2019-15741?
CVE-2019-15741 affects GitLab Omnibus versions from 7.4.0 to 12.2.1.
What consequences could result from exploiting CVE-2019-15741?
Exploitation of CVE-2019-15741 could allow an unauthorized user to gain elevated privileges on the affected system.
Is there a workaround for CVE-2019-15741?
Currently, there is no known workaround for CVE-2019-15741; upgrading is the recommended action.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/author
agent/first-publish-date
agent/description
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/7.4.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-15741?
CVE-2019-15741 is classified as a medium severity vulnerability that can lead to privilege escalation.
How do I fix CVE-2019-15741?
To fix CVE-2019-15741, you should upgrade your GitLab Omnibus installation to version 12.2.3 or later.
Which versions of GitLab Omnibus are affected by CVE-2019-15741?
CVE-2019-15741 affects GitLab Omnibus versions from 7.4.0 to 12.2.1.
What consequences could result from exploiting CVE-2019-15741?
Exploitation of CVE-2019-15741 could allow an unauthorized user to gain elevated privileges on the affected system.
Is there a workaround for CVE-2019-15741?
Currently, there is no known workaround for CVE-2019-15741; upgrading is the recommended action.