What is the severity of CVE-2018-17451?

CVE-2018-17451 is classified as a medium severity vulnerability due to its Cross Site Request Forgery (CSRF) risk in Slack integration.

How do I fix CVE-2018-17451?

To fix CVE-2018-17451, upgrade GitLab to version 11.1.7, 11.2.4, or 11.3.1 or later.

What versions of GitLab are affected by CVE-2018-17451?

CVE-2018-17451 affects GitLab Community and Enterprise Editions prior to versions 11.1.7, 11.2.4, and 11.3.1.

What type of vulnerability is CVE-2018-17451?

CVE-2018-17451 is a Cross Site Request Forgery (CSRF) vulnerability impacting the Slack integration.

Is the Slack integration the only affected feature in CVE-2018-17451?

Yes, the vulnerability specifically affects the Slack integration for issuing slash commands within GitLab.

Vulnerability/
CVE-2018-17451

high

8.8

CWE

352

15/4/2023

5/8/2024

CVE-2018-17451: CSRF

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. There is Cross Site Request Forgery (CSRF) in the Slack integration for issuing slash commands.

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-17451?
CVE-2018-17451 is classified as a medium severity vulnerability due to its Cross Site Request Forgery (CSRF) risk in Slack integration.
How do I fix CVE-2018-17451?
To fix CVE-2018-17451, upgrade GitLab to version 11.1.7, 11.2.4, or 11.3.1 or later.
What versions of GitLab are affected by CVE-2018-17451?
CVE-2018-17451 affects GitLab Community and Enterprise Editions prior to versions 11.1.7, 11.2.4, and 11.3.1.
What type of vulnerability is CVE-2018-17451?
CVE-2018-17451 is a Cross Site Request Forgery (CSRF) vulnerability impacting the Slack integration.
Is the Slack integration the only affected feature in CVE-2018-17451?
Yes, the vulnerability specifically affects the Slack integration for issuing slash commands within GitLab.

agent/references
agent/type
agent/author
agent/weakness
agent/severity
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-17451?
CVE-2018-17451 is classified as a medium severity vulnerability due to its Cross Site Request Forgery (CSRF) risk in Slack integration.
How do I fix CVE-2018-17451?
To fix CVE-2018-17451, upgrade GitLab to version 11.1.7, 11.2.4, or 11.3.1 or later.
What versions of GitLab are affected by CVE-2018-17451?
CVE-2018-17451 affects GitLab Community and Enterprise Editions prior to versions 11.1.7, 11.2.4, and 11.3.1.
What type of vulnerability is CVE-2018-17451?
CVE-2018-17451 is a Cross Site Request Forgery (CSRF) vulnerability impacting the Slack integration.
Is the Slack integration the only affected feature in CVE-2018-17451?
Yes, the vulnerability specifically affects the Slack integration for issuing slash commands within GitLab.