What is the severity of CVE-2018-18646?

CVE-2018-18646 is considered a high severity vulnerability due to its potential for SSRF attacks.

How do I fix CVE-2018-18646?

To fix CVE-2018-18646, you should upgrade GitLab to version 11.2.7, 11.3.8, or 11.4.3, or later.

What types of GitLab installations are affected by CVE-2018-18646?

CVE-2018-18646 affects both the GitLab Community and Enterprise Editions before the specified patched versions.

Can CVE-2018-18646 lead to data breaches?

Yes, CVE-2018-18646 can lead to unauthorized access to local services and may potentially result in data breaches.

What is SSRF in the context of CVE-2018-18646?

SSRF, or Server-Side Request Forgery, is a vulnerability that allows an attacker to induce a server-side application to make requests to an unintended location.

Vulnerability/
CVE-2018-18646

high

8.8

CWE

918

4/12/2018

5/8/2024

CVE-2018-18646: SSRF

First published: Tue Dec 04 2018(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.2.7, 11.3.x before 11.3.8, and 11.4.x before 11.4.3. It allows SSRF.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=5.3<11.2.7
GitLab	>=5.3<11.2.7
GitLab	>=11.3.0<11.3.8
GitLab	>=11.3.0<11.3.8
GitLab	>=11.4.0<11.4.3
GitLab	>=11.4.0<11.4.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-18646?
CVE-2018-18646 is considered a high severity vulnerability due to its potential for SSRF attacks.
How do I fix CVE-2018-18646?
To fix CVE-2018-18646, you should upgrade GitLab to version 11.2.7, 11.3.8, or 11.4.3, or later.
What types of GitLab installations are affected by CVE-2018-18646?
CVE-2018-18646 affects both the GitLab Community and Enterprise Editions before the specified patched versions.
Can CVE-2018-18646 lead to data breaches?
Yes, CVE-2018-18646 can lead to unauthorized access to local services and may potentially result in data breaches.
What is SSRF in the context of CVE-2018-18646?
SSRF, or Server-Side Request Forgery, is a vulnerability that allows an attacker to induce a server-side application to make requests to an unintended location.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/5.3
version/gitlab/11.3.0
version/gitlab/11.4.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-18646?
CVE-2018-18646 is considered a high severity vulnerability due to its potential for SSRF attacks.
How do I fix CVE-2018-18646?
To fix CVE-2018-18646, you should upgrade GitLab to version 11.2.7, 11.3.8, or 11.4.3, or later.
What types of GitLab installations are affected by CVE-2018-18646?
CVE-2018-18646 affects both the GitLab Community and Enterprise Editions before the specified patched versions.
Can CVE-2018-18646 lead to data breaches?
Yes, CVE-2018-18646 can lead to unauthorized access to local services and may potentially result in data breaches.
What is SSRF in the context of CVE-2018-18646?
SSRF, or Server-Side Request Forgery, is a vulnerability that allows an attacker to induce a server-side application to make requests to an unintended location.