What is the severity of CVE-2020-13319?

CVE-2020-13319 has been classified as a medium severity vulnerability.

How do I fix CVE-2020-13319?

To remediate CVE-2020-13319, upgrade GitLab to version 13.1.2 or later, 13.0.8, or 12.10.13.

What is the impact of CVE-2020-13319?

The impact of CVE-2020-13319 is that users may add time spent on an issue without proper permission checks.

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

CVE-2020-13319 affects GitLab versions prior to 13.1.2, 13.0.8, and 12.10.13.

Is there a workaround for CVE-2020-13319?

There is no official workaround for CVE-2020-13319; the only solution is to upgrade to the patched versions.

Vulnerability/
CVE-2020-13319

medium

4.3

CWE

862

29/9/2020

4/8/2024

CVE-2020-13319

First published: Tue Sep 29 2020(Updated: )

An issue has been discovered in GitLab affecting versions prior to 13.1.2, 13.0.8 and 12.10.13. Missing permission check for adding time spent on an issue.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<12.10.13
GitLab	>=13.0.0<13.0.8
GitLab	>=13.1.0<13.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13319?
CVE-2020-13319 has been classified as a medium severity vulnerability.
How do I fix CVE-2020-13319?
To remediate CVE-2020-13319, upgrade GitLab to version 13.1.2 or later, 13.0.8, or 12.10.13.
What is the impact of CVE-2020-13319?
The impact of CVE-2020-13319 is that users may add time spent on an issue without proper permission checks.
Which versions of GitLab are affected by CVE-2020-13319?
CVE-2020-13319 affects GitLab versions prior to 13.1.2, 13.0.8, and 12.10.13.
Is there a workaround for CVE-2020-13319?
There is no official workaround for CVE-2020-13319; the only solution is to upgrade to the patched versions.

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/13.0.0
version/gitlab/13.1.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-13319?
CVE-2020-13319 has been classified as a medium severity vulnerability.
How do I fix CVE-2020-13319?
To remediate CVE-2020-13319, upgrade GitLab to version 13.1.2 or later, 13.0.8, or 12.10.13.
What is the impact of CVE-2020-13319?
The impact of CVE-2020-13319 is that users may add time spent on an issue without proper permission checks.
Which versions of GitLab are affected by CVE-2020-13319?
CVE-2020-13319 affects GitLab versions prior to 13.1.2, 13.0.8, and 12.10.13.
Is there a workaround for CVE-2020-13319?
There is no official workaround for CVE-2020-13319; the only solution is to upgrade to the patched versions.