CVE-2019-5469
First published: Wed Dec 18 2019(Updated: )
An IDOR vulnerability exists in GitLab <v12.1.2, <v12.0.4, and <v11.11.6 that allowed uploading files from project archive to replace other users files potentially allowing an attacker to replace project binaries or other uploaded assets.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.11.0<11.11.6 | |
| GitLab | >=11.11.0<11.11.6 | |
| GitLab | >=12.0.0<12.0.4 | |
| GitLab | >=12.0.0<12.0.4 | |
| GitLab | >=12.1.0<12.1.2 | |
| GitLab | >=12.1.0<12.1.2 |
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-5469?
CVE-2019-5469 is rated as a high severity vulnerability that allows unauthorized file replacements in GitLab.
How do I fix CVE-2019-5469?
To fix CVE-2019-5469, upgrade your GitLab instance to versions 12.1.3, 12.0.5, or 11.11.7 or later.
What is the impact of CVE-2019-5469?
The impact of CVE-2019-5469 includes potential data integrity issues through unauthorized file replacements.
Which versions of GitLab are affected by CVE-2019-5469?
CVE-2019-5469 affects GitLab versions prior to 12.1.3, 12.0.5, and 11.11.7.
Is there a workaround for CVE-2019-5469?
There are no known workarounds for CVE-2019-5469, so the recommended action is to perform the necessary software upgrade.
- 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/11.11.0
- version/gitlab/12.0.0
- version/gitlab/12.1.0