What is the severity of CVE-2018-17449?

CVE-2018-17449 has a medium severity rating due to the potential exposure of sensitive information.

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.

What type of vulnerability is CVE-2018-17449?

CVE-2018-17449 is categorized as an insecure direct object reference vulnerability.

What information could be exposed due to CVE-2018-17449?

CVE-2018-17449 could expose sensitive information about issues, comments, and project titles.

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.

Vulnerability/
CVE-2018-17449

high

7.5

CWE

639

15/4/2023

5/8/2024

CVE-2018-17449

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. Remote attackers could obtain sensitive information about issues, comments, and project titles via events API insecure direct object reference.

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

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-17449?
CVE-2018-17449 has a medium severity rating due to the potential exposure of sensitive information.
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.
What type of vulnerability is CVE-2018-17449?
CVE-2018-17449 is categorized as an insecure direct object reference vulnerability.
What information could be exposed due to CVE-2018-17449?
CVE-2018-17449 could expose sensitive information about issues, comments, and project titles.
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.

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.2.0
version/gitlab/11.3.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-2018-17449?
CVE-2018-17449 has a medium severity rating due to the potential exposure of sensitive information.
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.
What type of vulnerability is CVE-2018-17449?
CVE-2018-17449 is categorized as an insecure direct object reference vulnerability.
What information could be exposed due to CVE-2018-17449?
CVE-2018-17449 could expose sensitive information about issues, comments, and project titles.
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.