CVE-2019-19259
First published: Fri Jan 03 2020(Updated: )
GitLab Enterprise Edition (EE) 11.3 and later through 12.5 allows an Insecure Direct Object Reference (IDOR).
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.3.0<12.5.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-19259?
CVE-2019-19259 has a medium severity rating due to the potential for unauthorized access through Insecure Direct Object Reference.
How do I fix CVE-2019-19259?
To fix CVE-2019-19259, update GitLab Enterprise Edition to version 12.5.1 or later.
What versions of GitLab are affected by CVE-2019-19259?
GitLab Enterprise Edition versions 11.3 to 12.5 are affected by CVE-2019-19259.
What type of vulnerability is CVE-2019-19259?
CVE-2019-19259 is classified as an Insecure Direct Object Reference (IDOR) vulnerability.
What impact does CVE-2019-19259 have on security?
CVE-2019-19259 may allow attackers to access or modify objects they should not have permissions for, leading to potential data exposure.
- 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/11.3.0