What is the severity of CVE-2018-19580?

CVE-2018-19580 is classified as a medium severity vulnerability due to the potential risk of unauthorized access when email addresses are changed without proper notification.

How do I fix CVE-2018-19580?

To fix CVE-2018-19580, upgrade GitLab to version 11.5.1 or later, 11.4.8, or 11.3.11.

Who is affected by CVE-2018-19580?

CVE-2018-19580 affects all versions of GitLab prior to 11.5.1, 11.4.8, and 11.3.11.

What does CVE-2018-19580 impact in GitLab?

CVE-2018-19580 impacts the email notification feature during an email address change, failing to notify the old email address of the change.

Is there a workaround for CVE-2018-19580?

There is no official workaround for CVE-2018-19580; upgrading to the patched versions is the recommended solution.

Vulnerability/
CVE-2018-19580

medium

5.3

CWE

10/7/2019

5/8/2024

CVE-2018-19580: Input Validation

First published: Wed Jul 10 2019(Updated: )

All versions of GitLab prior to 11.5.1, 11.4.8, and 11.3.11 do not send an email to the old email address when an email address change is made.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.3.11
GitLab	<11.3.11
GitLab	>=11.3.12<11.4.8
GitLab	>=11.3.12<11.4.8
GitLab	>=11.4.9<11.5.1
GitLab	>=11.4.9<11.5.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-19580?
CVE-2018-19580 is classified as a medium severity vulnerability due to the potential risk of unauthorized access when email addresses are changed without proper notification.
How do I fix CVE-2018-19580?
To fix CVE-2018-19580, upgrade GitLab to version 11.5.1 or later, 11.4.8, or 11.3.11.
Who is affected by CVE-2018-19580?
CVE-2018-19580 affects all versions of GitLab prior to 11.5.1, 11.4.8, and 11.3.11.
What does CVE-2018-19580 impact in GitLab?
CVE-2018-19580 impacts the email notification feature during an email address change, failing to notify the old email address of the change.
Is there a workaround for CVE-2018-19580?
There is no official workaround for CVE-2018-19580; upgrading to the patched versions is the recommended solution.

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/11.3.12
version/gitlab/11.4.9

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-19580?
CVE-2018-19580 is classified as a medium severity vulnerability due to the potential risk of unauthorized access when email addresses are changed without proper notification.
How do I fix CVE-2018-19580?
To fix CVE-2018-19580, upgrade GitLab to version 11.5.1 or later, 11.4.8, or 11.3.11.
Who is affected by CVE-2018-19580?
CVE-2018-19580 affects all versions of GitLab prior to 11.5.1, 11.4.8, and 11.3.11.
What does CVE-2018-19580 impact in GitLab?
CVE-2018-19580 impacts the email notification feature during an email address change, failing to notify the old email address of the change.
Is there a workaround for CVE-2018-19580?
There is no official workaround for CVE-2018-19580; upgrading to the patched versions is the recommended solution.