What is the severity of CVE-2020-13314?

CVE-2020-13314 is classified as a medium severity vulnerability.

How do I fix CVE-2020-13314?

To fix CVE-2020-13314, upgrade GitLab to version 13.1.10, 13.2.8, or 13.3.4 or later.

What is the impact of CVE-2020-13314?

CVE-2020-13314 allows a malicious user to submit content that can lead to displayed error messages, potentially disclosing sensitive information.

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

CVE-2020-13314 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.

Is CVE-2020-13314 relevant to both community and enterprise GitLab versions?

Yes, CVE-2020-13314 affects both community and enterprise editions of GitLab.

Vulnerability/
CVE-2020-13314

medium

5.3

CWE

14/9/2020

4/8/2024

CVE-2020-13314: Input Validation

First published: Mon Sep 14 2020(Updated: )

A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. GitLab Omniauth endpoint allowed a malicious user to submit content to be displayed back to the user within error messages.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.1.0<13.1.10
GitLab	>=13.1.0<13.1.10
GitLab	>=13.2.0<13.2.8
GitLab	>=13.2.0<13.2.8
GitLab	>=13.3.0<13.3.4
GitLab	>=13.3.0<13.3.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13314?
CVE-2020-13314 is classified as a medium severity vulnerability.
How do I fix CVE-2020-13314?
To fix CVE-2020-13314, upgrade GitLab to version 13.1.10, 13.2.8, or 13.3.4 or later.
What is the impact of CVE-2020-13314?
CVE-2020-13314 allows a malicious user to submit content that can lead to displayed error messages, potentially disclosing sensitive information.
Which versions of GitLab are affected by CVE-2020-13314?
CVE-2020-13314 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
Is CVE-2020-13314 relevant to both community and enterprise GitLab versions?
Yes, CVE-2020-13314 affects both community and enterprise editions of GitLab.

agent/type
agent/references
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/weakness
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/13.1.0
version/gitlab/13.2.0
version/gitlab/13.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-2020-13314?
CVE-2020-13314 is classified as a medium severity vulnerability.
How do I fix CVE-2020-13314?
To fix CVE-2020-13314, upgrade GitLab to version 13.1.10, 13.2.8, or 13.3.4 or later.
What is the impact of CVE-2020-13314?
CVE-2020-13314 allows a malicious user to submit content that can lead to displayed error messages, potentially disclosing sensitive information.
Which versions of GitLab are affected by CVE-2020-13314?
CVE-2020-13314 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
Is CVE-2020-13314 relevant to both community and enterprise GitLab versions?
Yes, CVE-2020-13314 affects both community and enterprise editions of GitLab.