What is the severity of CVE-2019-19313?

CVE-2019-19313 has been classified as a Denial of Service vulnerability.

How do I fix CVE-2019-19313?

To resolve CVE-2019-19313, upgrade GitLab to version 12.5.1 or later.

Which versions of GitLab are affected by CVE-2019-19313?

CVE-2019-19313 affects GitLab versions 12.3 through 12.5, as well as specific versions 12.4.3 and 12.3.6.

What impact does CVE-2019-19313 have on GitLab users?

CVE-2019-19313 prevents users from creating, editing, or viewing issues and commits.

Is CVE-2019-19313 a critical vulnerability?

While not classified as critical, CVE-2019-19313 can significantly disrupt functionality in affected GitLab versions.

Vulnerability/
CVE-2019-19313

high

7.5

CWE

755

5/1/2020

5/8/2024

CVE-2019-19313

First published: Sun Jan 05 2020(Updated: )

GitLab EE 12.3 through 12.5, 12.4.3, and 12.3.6 allows Denial of Service. Certain characters were making it impossible to create, edit, or view issues and commits.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=12.3.0<12.3.8
GitLab	>=12.4.0<12.4.5
GitLab	>=12.5.0<12.5.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-19313?
CVE-2019-19313 has been classified as a Denial of Service vulnerability.
How do I fix CVE-2019-19313?
To resolve CVE-2019-19313, upgrade GitLab to version 12.5.1 or later.
Which versions of GitLab are affected by CVE-2019-19313?
CVE-2019-19313 affects GitLab versions 12.3 through 12.5, as well as specific versions 12.4.3 and 12.3.6.
What impact does CVE-2019-19313 have on GitLab users?
CVE-2019-19313 prevents users from creating, editing, or viewing issues and commits.
Is CVE-2019-19313 a critical vulnerability?
While not classified as critical, CVE-2019-19313 can significantly disrupt functionality in affected GitLab versions.

agent/type
agent/references
agent/severity
agent/weakness
agent/author
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/12.3.0
version/gitlab/12.4.0
version/gitlab/12.5.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-2019-19313?
CVE-2019-19313 has been classified as a Denial of Service vulnerability.
How do I fix CVE-2019-19313?
To resolve CVE-2019-19313, upgrade GitLab to version 12.5.1 or later.
Which versions of GitLab are affected by CVE-2019-19313?
CVE-2019-19313 affects GitLab versions 12.3 through 12.5, as well as specific versions 12.4.3 and 12.3.6.
What impact does CVE-2019-19313 have on GitLab users?
CVE-2019-19313 prevents users from creating, editing, or viewing issues and commits.
Is CVE-2019-19313 a critical vulnerability?
While not classified as critical, CVE-2019-19313 can significantly disrupt functionality in affected GitLab versions.