CVE-2018-17453
First published: Sat Apr 15 2023(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. Attackers may have been able to obtain sensitive access-token data from Sentry logs via the GRPC::Unknown exception.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <11.1.7 | |
| GitLab | <11.1.7 | |
| GitLab | >=11.2.0<11.2.4 | |
| GitLab | >=11.2.0<11.2.4 | |
| GitLab | =11.3.0 | |
| GitLab | =11.3.0 |
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-2018-17453?
CVE-2018-17453 is rated as a moderate severity vulnerability due to the potential exposure of sensitive access-token data.
How do I fix CVE-2018-17453?
To fix CVE-2018-17453, upgrade your GitLab Community or Enterprise Edition to version 11.1.7 or later, or to version 11.2.4 or later.
What versions are affected by CVE-2018-17453?
CVE-2018-17453 affects GitLab Community and Enterprise Editions prior to versions 11.1.7, 11.2.4, and 11.3.1.
What types of data could be compromised by CVE-2018-17453?
CVE-2018-17453 could allow attackers to access sensitive access-token data from Sentry logs.
In which software can I find CVE-2018-17453?
CVE-2018-17453 is found in GitLab Community and Enterprise Editions.
- agent/references
- agent/type
- agent/severity
- agent/author
- 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.2.0
- version/gitlab/11.3.0