CVE-2018-17449: High severity gitlab vulnerability
Published 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. Remote attackers could obtain sensitive information about issues, comments, and project titles via events API insecure direct object reference.
Affected Software
6 affected components
GitLab GitLab<11.1.7
GitLab GitLab<11.1.7
GitLab GitLab>=11.2.0<11.2.4
GitLab GitLab>=11.2.0<11.2.4
GitLab GitLab=11.3.0
GitLab GitLab=11.3.0
Event History
Apr 15, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2018-17449?
CVE-2018-17449 has a medium severity rating due to the potential exposure of sensitive information.
2
How do I fix CVE-2018-17449?
To fix CVE-2018-17449, upgrade to GitLab versions 11.1.7, 11.2.4, or 11.3.1 or later.
3
What type of vulnerability is CVE-2018-17449?
CVE-2018-17449 is categorized as an insecure direct object reference vulnerability.
4
What information could be exposed due to CVE-2018-17449?
CVE-2018-17449 could expose sensitive information about issues, comments, and project titles.
5
Which versions of GitLab are affected by CVE-2018-17449?
CVE-2018-17449 affects GitLab versions before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1.