What is the severity of CVE-2020-13266?

CVE-2020-13266 has been classified with a medium severity rating due to the potential for unauthorized modification of deploy key permissions.

How do I fix CVE-2020-13266?

To fix CVE-2020-13266, upgrade GitLab CE/EE to version 13.0.2 or later to mitigate the insecure authorization issue.

Who is affected by CVE-2020-13266?

CVE-2020-13266 affects users of GitLab CE/EE versions 12.8 to 13.0.1, allowing them to potentially alter the permissions of deploy keys belonging to other users.

What happens if CVE-2020-13266 is exploited?

If exploited, CVE-2020-13266 could allow a user to change the access permissions of another user's deploy keys, leading to unauthorized access.

Is there a workaround for CVE-2020-13266?

Currently, there is no known workaround for CVE-2020-13266; the recommended action is to upgrade to a fixed version of GitLab.

Vulnerability/
CVE-2020-13266

medium

4.3

CWE

862

9/6/2020

4/8/2024

CVE-2020-13266

First published: Tue Jun 09 2020(Updated: )

Insecure authorization in Project Deploy Keys in GitLab CE/EE 12.8 and later through 13.0.1 allows users to update permissions of other users' deploy keys under certain conditions

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.8<=13.0.1
GitLab	>=12.8<=13.0.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13266?
CVE-2020-13266 has been classified with a medium severity rating due to the potential for unauthorized modification of deploy key permissions.
How do I fix CVE-2020-13266?
To fix CVE-2020-13266, upgrade GitLab CE/EE to version 13.0.2 or later to mitigate the insecure authorization issue.
Who is affected by CVE-2020-13266?
CVE-2020-13266 affects users of GitLab CE/EE versions 12.8 to 13.0.1, allowing them to potentially alter the permissions of deploy keys belonging to other users.
What happens if CVE-2020-13266 is exploited?
If exploited, CVE-2020-13266 could allow a user to change the access permissions of another user's deploy keys, leading to unauthorized access.
Is there a workaround for CVE-2020-13266?
Currently, there is no known workaround for CVE-2020-13266; the recommended action is to upgrade to a fixed version of GitLab.

agent/references
agent/type
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
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/12.8
version/gitlab/13.0.1

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-2020-13266?
CVE-2020-13266 has been classified with a medium severity rating due to the potential for unauthorized modification of deploy key permissions.
How do I fix CVE-2020-13266?
To fix CVE-2020-13266, upgrade GitLab CE/EE to version 13.0.2 or later to mitigate the insecure authorization issue.
Who is affected by CVE-2020-13266?
CVE-2020-13266 affects users of GitLab CE/EE versions 12.8 to 13.0.1, allowing them to potentially alter the permissions of deploy keys belonging to other users.
What happens if CVE-2020-13266 is exploited?
If exploited, CVE-2020-13266 could allow a user to change the access permissions of another user's deploy keys, leading to unauthorized access.
Is there a workaround for CVE-2020-13266?
Currently, there is no known workaround for CVE-2020-13266; the recommended action is to upgrade to a fixed version of GitLab.