What is the severity of CVE-2019-9221?

The severity of CVE-2019-9221 is classified as high due to the incorrect access control vulnerability.

How do I fix CVE-2019-9221?

To fix CVE-2019-9221, you need to upgrade GitLab to version 11.6.10 or later for community and enterprise editions.

What versions are affected by CVE-2019-9221?

CVE-2019-9221 affects GitLab Community and Enterprise Editions before version 11.6.10, and versions 11.7.0 to 11.7.5, and 11.8.0 to 11.8.0.

What type of vulnerability is CVE-2019-9221?

CVE-2019-9221 is categorized as an incorrect access control vulnerability.

Is CVE-2019-9221 specific to GitLab Community Edition?

No, CVE-2019-9221 affects both GitLab Community Edition and Enterprise Edition.

Vulnerability/
CVE-2019-9221

medium

5.5

CWE

29/5/2019

4/8/2024

CVE-2019-9221: Input Validation

First published: Wed May 29 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It has Incorrect Access Control (issue 3 of 5).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.6.10
GitLab	<11.6.10
GitLab	>=11.7.0<11.7.6
GitLab	>=11.7.0<11.7.6
GitLab	>=11.8.0<11.8.1
GitLab	>=11.8.0<11.8.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-9221?
The severity of CVE-2019-9221 is classified as high due to the incorrect access control vulnerability.
How do I fix CVE-2019-9221?
To fix CVE-2019-9221, you need to upgrade GitLab to version 11.6.10 or later for community and enterprise editions.
What versions are affected by CVE-2019-9221?
CVE-2019-9221 affects GitLab Community and Enterprise Editions before version 11.6.10, and versions 11.7.0 to 11.7.5, and 11.8.0 to 11.8.0.
What type of vulnerability is CVE-2019-9221?
CVE-2019-9221 is categorized as an incorrect access control vulnerability.
Is CVE-2019-9221 specific to GitLab Community Edition?
No, CVE-2019-9221 affects both GitLab Community Edition and Enterprise Edition.

agent/type
agent/references
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.7.0
version/gitlab/11.8.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-2019-9221?
The severity of CVE-2019-9221 is classified as high due to the incorrect access control vulnerability.
How do I fix CVE-2019-9221?
To fix CVE-2019-9221, you need to upgrade GitLab to version 11.6.10 or later for community and enterprise editions.
What versions are affected by CVE-2019-9221?
CVE-2019-9221 affects GitLab Community and Enterprise Editions before version 11.6.10, and versions 11.7.0 to 11.7.5, and 11.8.0 to 11.8.0.
What type of vulnerability is CVE-2019-9221?
CVE-2019-9221 is categorized as an incorrect access control vulnerability.
Is CVE-2019-9221 specific to GitLab Community Edition?
No, CVE-2019-9221 affects both GitLab Community Edition and Enterprise Edition.