What is the severity of CVE-2018-19571?

CVE-2018-19571 is classified as a medium severity vulnerability due to its SSRF nature.

How do I fix CVE-2018-19571?

To fix CVE-2018-19571, upgrade GitLab to versions 11.3.11, 11.4.8, or 11.5.1 or later.

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

CVE-2018-19571 affects GitLab CE/EE versions from 8.18 up to, but not including, 11.3.11, 11.4 up to 11.4.8, and 11.5 up to 11.5.1.

What is an SSRF vulnerability in the context of CVE-2018-19571?

In the context of CVE-2018-19571, an SSRF vulnerability allows an attacker to make requests from the server, potentially accessing internal services.

Is there a way to mitigate CVE-2018-19571 besides upgrading?

Mitigation strategies for CVE-2018-19571 may include network segmentation and implementing firewall rules to limit server communication.

Vulnerability/
CVE-2018-19571

high

7.7

CWE

918

10/7/2019

5/8/2024

CVE-2018-19571: SSRF

First published: Wed Jul 10 2019(Updated: )

GitLab CE/EE, versions 8.18 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an SSRF vulnerability in webhooks.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.18.0<11.3.11
GitLab	>=8.18.0<11.3.11
GitLab	>=11.4.0<11.4.8
GitLab	>=11.4.0<11.4.8
GitLab	>=11.5.0<11.5.1
GitLab	>=11.5.0<11.5.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-19571?
CVE-2018-19571 is classified as a medium severity vulnerability due to its SSRF nature.
How do I fix CVE-2018-19571?
To fix CVE-2018-19571, upgrade GitLab to versions 11.3.11, 11.4.8, or 11.5.1 or later.
Which versions of GitLab are affected by CVE-2018-19571?
CVE-2018-19571 affects GitLab CE/EE versions from 8.18 up to, but not including, 11.3.11, 11.4 up to 11.4.8, and 11.5 up to 11.5.1.
What is an SSRF vulnerability in the context of CVE-2018-19571?
In the context of CVE-2018-19571, an SSRF vulnerability allows an attacker to make requests from the server, potentially accessing internal services.
Is there a way to mitigate CVE-2018-19571 besides upgrading?
Mitigation strategies for CVE-2018-19571 may include network segmentation and implementing firewall rules to limit server communication.

agent/references
agent/type
agent/weakness
agent/author
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/8.18.0
version/gitlab/11.4.0
version/gitlab/11.5.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-19571?
CVE-2018-19571 is classified as a medium severity vulnerability due to its SSRF nature.
How do I fix CVE-2018-19571?
To fix CVE-2018-19571, upgrade GitLab to versions 11.3.11, 11.4.8, or 11.5.1 or later.
Which versions of GitLab are affected by CVE-2018-19571?
CVE-2018-19571 affects GitLab CE/EE versions from 8.18 up to, but not including, 11.3.11, 11.4 up to 11.4.8, and 11.5 up to 11.5.1.
What is an SSRF vulnerability in the context of CVE-2018-19571?
In the context of CVE-2018-19571, an SSRF vulnerability allows an attacker to make requests from the server, potentially accessing internal services.
Is there a way to mitigate CVE-2018-19571 besides upgrading?
Mitigation strategies for CVE-2018-19571 may include network segmentation and implementing firewall rules to limit server communication.