What is the severity of CVE-2018-19496?

CVE-2018-19496 has a medium severity due to the potential for unauthorized promotion of project milestones.

How do I fix CVE-2018-19496?

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

Which versions are affected by CVE-2018-19496?

CVE-2018-19496 affects GitLab Community and Enterprise Edition versions 10.x and 11.x prior to 11.3.11, 11.4.x prior to 11.4.8, and 11.5.x prior to 11.5.1.

What type of vulnerability is CVE-2018-19496?

CVE-2018-19496 is an incorrect access control vulnerability.

Can CVE-2018-19496 lead to privilege escalation?

Yes, CVE-2018-19496 can lead to privilege escalation by allowing users with insufficient rights to promote milestones.

Vulnerability/
CVE-2018-19496

medium

6.5

CWE

284

10/7/2019

5/8/2024

CVE-2018-19496

First published: Wed Jul 10 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 10.x and 11.x before 11.3.11, 11.4.x before 11.4.8, and 11.5.x before 11.5.1. There is an incorrect access control vulnerability that permits a user with insufficient privileges to promote a project milestone to a group milestone.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=10.0.0<11.3.11
GitLab	>=10.0.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-19496?
CVE-2018-19496 has a medium severity due to the potential for unauthorized promotion of project milestones.
How do I fix CVE-2018-19496?
To fix CVE-2018-19496, upgrade GitLab to version 11.3.11, 11.4.8 or 11.5.1 or later.
Which versions are affected by CVE-2018-19496?
CVE-2018-19496 affects GitLab Community and Enterprise Edition versions 10.x and 11.x prior to 11.3.11, 11.4.x prior to 11.4.8, and 11.5.x prior to 11.5.1.
What type of vulnerability is CVE-2018-19496?
CVE-2018-19496 is an incorrect access control vulnerability.
Can CVE-2018-19496 lead to privilege escalation?
Yes, CVE-2018-19496 can lead to privilege escalation by allowing users with insufficient rights to promote milestones.

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/10.0.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-19496?
CVE-2018-19496 has a medium severity due to the potential for unauthorized promotion of project milestones.
How do I fix CVE-2018-19496?
To fix CVE-2018-19496, upgrade GitLab to version 11.3.11, 11.4.8 or 11.5.1 or later.
Which versions are affected by CVE-2018-19496?
CVE-2018-19496 affects GitLab Community and Enterprise Edition versions 10.x and 11.x prior to 11.3.11, 11.4.x prior to 11.4.8, and 11.5.x prior to 11.5.1.
What type of vulnerability is CVE-2018-19496?
CVE-2018-19496 is an incorrect access control vulnerability.
Can CVE-2018-19496 lead to privilege escalation?
Yes, CVE-2018-19496 can lead to privilege escalation by allowing users with insufficient rights to promote milestones.