What is the severity of CVE-2019-9485?

CVE-2019-9485 has been classified as a medium severity vulnerability due to its potential impact on sensitive data.

How do I fix CVE-2019-9485?

To fix CVE-2019-9485, upgrade GitLab to version 11.6.10, 11.7.6, or 11.8.1 or later.

What versions are affected by CVE-2019-9485?

CVE-2019-9485 affects GitLab Community and Enterprise Edition versions prior to 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.

What are the implications of CVE-2019-9485?

The implications of CVE-2019-9485 include potential unauthorized access to sensitive data due to insecure permissions.

Is CVE-2019-9485 exploitable remotely?

Yes, CVE-2019-9485 is exploitable remotely, which increases the risk of unauthorized access to the affected systems.

Vulnerability/
CVE-2019-9485

critical

9.8

29/5/2019

4/8/2024

CVE-2019-9485

First published: Wed May 29 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It has Insecure Permissions.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.6.10
GitLab	<11.6.10
GitLab	>=11.7.0<11.7.6
GitLab	>=11.7.0<11.7.6
GitLab	>=11.8.0<11.8.1
GitLab	>=11.8.0<11.8.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-9485?
CVE-2019-9485 has been classified as a medium severity vulnerability due to its potential impact on sensitive data.
How do I fix CVE-2019-9485?
To fix CVE-2019-9485, upgrade GitLab to version 11.6.10, 11.7.6, or 11.8.1 or later.
What versions are affected by CVE-2019-9485?
CVE-2019-9485 affects GitLab Community and Enterprise Edition versions prior to 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.
What are the implications of CVE-2019-9485?
The implications of CVE-2019-9485 include potential unauthorized access to sensitive data due to insecure permissions.
Is CVE-2019-9485 exploitable remotely?
Yes, CVE-2019-9485 is exploitable remotely, which increases the risk of unauthorized access to the affected systems.

agent/references
agent/type
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.7.0
version/gitlab/11.8.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-2019-9485?
CVE-2019-9485 has been classified as a medium severity vulnerability due to its potential impact on sensitive data.
How do I fix CVE-2019-9485?
To fix CVE-2019-9485, upgrade GitLab to version 11.6.10, 11.7.6, or 11.8.1 or later.
What versions are affected by CVE-2019-9485?
CVE-2019-9485 affects GitLab Community and Enterprise Edition versions prior to 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.
What are the implications of CVE-2019-9485?
The implications of CVE-2019-9485 include potential unauthorized access to sensitive data due to insecure permissions.
Is CVE-2019-9485 exploitable remotely?
Yes, CVE-2019-9485 is exploitable remotely, which increases the risk of unauthorized access to the affected systems.