What is the severity of CVE-2018-15472?

The severity of CVE-2018-15472 is considered moderate due to its impact on Sidekiq jobs in GitLab.

How do I fix CVE-2018-15472?

To fix CVE-2018-15472, upgrade to GitLab Community or Enterprise Edition version 11.1.7, 11.2.4, or 11.3.1 or later.

Which versions of GitLab are affected by CVE-2018-15472?

CVE-2018-15472 affects GitLab Community and Enterprise Editions prior to 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1.

What is the nature of the issue described in CVE-2018-15472?

The issue in CVE-2018-15472 involves the diff formatter using rouge that can block for extended periods in Sidekiq jobs without a timeout.

Is there a workaround for CVE-2018-15472 if immediate upgrade is not possible?

There are no documented workarounds for CVE-2018-15472, and upgrading is the recommended action.

Vulnerability/
CVE-2018-15472

high

7.5

15/4/2023

5/8/2024

CVE-2018-15472

First published: Sat Apr 15 2023(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. The diff formatter using rouge can block for a long time in Sidekiq jobs without any timeout.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.1.7
GitLab	<11.1.7
GitLab	>=11.2.0<11.2.4
GitLab	>=11.2.0<11.2.4
GitLab	=11.3.0
GitLab	=11.3.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-15472?
The severity of CVE-2018-15472 is considered moderate due to its impact on Sidekiq jobs in GitLab.
How do I fix CVE-2018-15472?
To fix CVE-2018-15472, upgrade to GitLab Community or Enterprise Edition version 11.1.7, 11.2.4, or 11.3.1 or later.
Which versions of GitLab are affected by CVE-2018-15472?
CVE-2018-15472 affects GitLab Community and Enterprise Editions prior to 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1.
What is the nature of the issue described in CVE-2018-15472?
The issue in CVE-2018-15472 involves the diff formatter using rouge that can block for extended periods in Sidekiq jobs without a timeout.
Is there a workaround for CVE-2018-15472 if immediate upgrade is not possible?
There are no documented workarounds for CVE-2018-15472, and upgrading is the recommended action.

agent/references
agent/type
agent/severity
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/11.2.0
version/gitlab/11.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.

Frequently Asked Questions

What is the severity of CVE-2018-15472?
The severity of CVE-2018-15472 is considered moderate due to its impact on Sidekiq jobs in GitLab.
How do I fix CVE-2018-15472?
To fix CVE-2018-15472, upgrade to GitLab Community or Enterprise Edition version 11.1.7, 11.2.4, or 11.3.1 or later.
Which versions of GitLab are affected by CVE-2018-15472?
CVE-2018-15472 affects GitLab Community and Enterprise Editions prior to 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1.
What is the nature of the issue described in CVE-2018-15472?
The issue in CVE-2018-15472 involves the diff formatter using rouge that can block for extended periods in Sidekiq jobs without a timeout.
Is there a workaround for CVE-2018-15472 if immediate upgrade is not possible?
There are no documented workarounds for CVE-2018-15472, and upgrading is the recommended action.