What is the severity of CVE-2019-13009?

CVE-2019-13009 has been classified as a medium severity vulnerability due to improper permissions allowing unauthorized access.

How do I fix CVE-2019-13009?

To fix CVE-2019-13009, users should update to GitLab versions 12.0.3 or later, which address the improper access control issue.

What types of installations are affected by CVE-2019-13009?

CVE-2019-13009 affects both GitLab Community and Enterprise Edition versions 9.2 to 12.0.2.

What kind of vulnerability is CVE-2019-13009?

CVE-2019-13009 is an access control vulnerability that allows unauthorized users to access uploaded files from unsaved personal snippets.

Who is responsible for exploiting the vulnerability described in CVE-2019-13009?

Exploitation of CVE-2019-13009 can be conducted by unauthorized users who leverage the improper permission settings in GitLab.

Vulnerability/
CVE-2019-13009

medium

6.5

CWE

400 732

10/3/2020

4/8/2024

CVE-2019-13009

First published: Tue Mar 10 2020(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 9.2 through 12.0.2. Uploaded files associated with unsaved personal snippets were accessible to unauthorized users due to improper permission settings. It has Incorrect Access Control.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=9.2.0<=12.0.2
GitLab	>=9.2.0<=12.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-13009?
CVE-2019-13009 has been classified as a medium severity vulnerability due to improper permissions allowing unauthorized access.
How do I fix CVE-2019-13009?
To fix CVE-2019-13009, users should update to GitLab versions 12.0.3 or later, which address the improper access control issue.
What types of installations are affected by CVE-2019-13009?
CVE-2019-13009 affects both GitLab Community and Enterprise Edition versions 9.2 to 12.0.2.
What kind of vulnerability is CVE-2019-13009?
CVE-2019-13009 is an access control vulnerability that allows unauthorized users to access uploaded files from unsaved personal snippets.
Who is responsible for exploiting the vulnerability described in CVE-2019-13009?
Exploitation of CVE-2019-13009 can be conducted by unauthorized users who leverage the improper permission settings in GitLab.

agent/weakness
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/9.2.0
version/gitlab/12.0.2

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-13009?
CVE-2019-13009 has been classified as a medium severity vulnerability due to improper permissions allowing unauthorized access.
How do I fix CVE-2019-13009?
To fix CVE-2019-13009, users should update to GitLab versions 12.0.3 or later, which address the improper access control issue.
What types of installations are affected by CVE-2019-13009?
CVE-2019-13009 affects both GitLab Community and Enterprise Edition versions 9.2 to 12.0.2.
What kind of vulnerability is CVE-2019-13009?
CVE-2019-13009 is an access control vulnerability that allows unauthorized users to access uploaded files from unsaved personal snippets.
Who is responsible for exploiting the vulnerability described in CVE-2019-13009?
Exploitation of CVE-2019-13009 can be conducted by unauthorized users who leverage the improper permission settings in GitLab.