What is the severity of CVE-2020-13286?

CVE-2020-13286 has a CVSS score indicating it is a high severity vulnerability due to its potential for Server Side Request Forgery.

How do I fix CVE-2020-13286?

Fix CVE-2020-13286 by upgrading GitLab to version 13.0.12, 13.1.6, or 13.2.3 or later.

What is the impact of CVE-2020-13286?

The impact of CVE-2020-13286 allows attackers to manipulate git configuration settings, leading to unauthorized requests to internal services.

Which versions of GitLab are affected by CVE-2020-13286?

CVE-2020-13286 affects GitLab versions prior to 13.0.12, 13.1.6, and 13.2.3 for both community and enterprise editions.

Who is affected by CVE-2020-13286?

Users running affected versions of GitLab, both community and enterprise, are at risk from CVE-2020-13286.

Vulnerability/
CVE-2020-13286

medium

6.4

CWE

918

13/8/2020

4/8/2024

CVE-2020-13286: SSRF

First published: Thu Aug 13 2020(Updated: )

For GitLab before 13.0.12, 13.1.6, 13.2.3 user controlled git configuration settings can be modified to result in Server Side Request Forgery.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.7.0<13.0.12
GitLab	>=12.7.0<13.0.12
GitLab	>=13.1.0<13.1.6
GitLab	>=13.1.0<13.1.6
GitLab	>=13.2.0<13.2.3
GitLab	>=13.2.0<13.2.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13286?
CVE-2020-13286 has a CVSS score indicating it is a high severity vulnerability due to its potential for Server Side Request Forgery.
How do I fix CVE-2020-13286?
Fix CVE-2020-13286 by upgrading GitLab to version 13.0.12, 13.1.6, or 13.2.3 or later.
What is the impact of CVE-2020-13286?
The impact of CVE-2020-13286 allows attackers to manipulate git configuration settings, leading to unauthorized requests to internal services.
Which versions of GitLab are affected by CVE-2020-13286?
CVE-2020-13286 affects GitLab versions prior to 13.0.12, 13.1.6, and 13.2.3 for both community and enterprise editions.
Who is affected by CVE-2020-13286?
Users running affected versions of GitLab, both community and enterprise, are at risk from CVE-2020-13286.

agent/type
agent/references
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.7.0
version/gitlab/13.1.0
version/gitlab/13.2.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-2020-13286?
CVE-2020-13286 has a CVSS score indicating it is a high severity vulnerability due to its potential for Server Side Request Forgery.
How do I fix CVE-2020-13286?
Fix CVE-2020-13286 by upgrading GitLab to version 13.0.12, 13.1.6, or 13.2.3 or later.
What is the impact of CVE-2020-13286?
The impact of CVE-2020-13286 allows attackers to manipulate git configuration settings, leading to unauthorized requests to internal services.
Which versions of GitLab are affected by CVE-2020-13286?
CVE-2020-13286 affects GitLab versions prior to 13.0.12, 13.1.6, and 13.2.3 for both community and enterprise editions.
Who is affected by CVE-2020-13286?
Users running affected versions of GitLab, both community and enterprise, are at risk from CVE-2020-13286.