What is the severity of CVE-2019-19256?

CVE-2019-19256 has a high severity due to its nature of incorrect access controls which can lead to unauthorized access.

How do I fix CVE-2019-19256?

To fix CVE-2019-19256, upgrade GitLab Enterprise Edition to version 12.5.1 or later.

What versions of GitLab are affected by CVE-2019-19256?

GitLab versions 12.2.0 to 12.5.0 are affected by CVE-2019-19256.

What type of vulnerability is CVE-2019-19256?

CVE-2019-19256 is classified as an access control vulnerability.

Can CVE-2019-19256 be exploited remotely?

Yes, CVE-2019-19256 can potentially be exploited remotely by unauthenticated attackers to gain unauthorized access.

Vulnerability/
CVE-2019-19256

medium

5.3

CWE

200

3/1/2020

5/8/2024

CVE-2019-19256: Infoleak

First published: Fri Jan 03 2020(Updated: )

GitLab Enterprise Edition (EE) 12.2 and later through 12.5 has Incorrect Access Control.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=12.2.0<12.5.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-19256?
CVE-2019-19256 has a high severity due to its nature of incorrect access controls which can lead to unauthorized access.
How do I fix CVE-2019-19256?
To fix CVE-2019-19256, upgrade GitLab Enterprise Edition to version 12.5.1 or later.
What versions of GitLab are affected by CVE-2019-19256?
GitLab versions 12.2.0 to 12.5.0 are affected by CVE-2019-19256.
What type of vulnerability is CVE-2019-19256?
CVE-2019-19256 is classified as an access control vulnerability.
Can CVE-2019-19256 be exploited remotely?
Yes, CVE-2019-19256 can potentially be exploited remotely by unauthenticated attackers to gain unauthorized access.

agent/references
agent/type
agent/weakness
agent/author
agent/severity
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/12.2.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-19256?
CVE-2019-19256 has a high severity due to its nature of incorrect access controls which can lead to unauthorized access.
How do I fix CVE-2019-19256?
To fix CVE-2019-19256, upgrade GitLab Enterprise Edition to version 12.5.1 or later.
What versions of GitLab are affected by CVE-2019-19256?
GitLab versions 12.2.0 to 12.5.0 are affected by CVE-2019-19256.
What type of vulnerability is CVE-2019-19256?
CVE-2019-19256 is classified as an access control vulnerability.
Can CVE-2019-19256 be exploited remotely?
Yes, CVE-2019-19256 can potentially be exploited remotely by unauthenticated attackers to gain unauthorized access.