What is the severity of CVE-2019-6785?

CVE-2019-6785 has a severity rating that indicates it allows for a Denial of Service attack in affected GitLab versions.

How do I fix CVE-2019-6785?

To fix CVE-2019-6785, you should upgrade your GitLab installation to version 11.5.8, 11.6.6, or 11.7.1 or newer.

Which versions are affected by CVE-2019-6785?

CVE-2019-6785 affects GitLab Community and Enterprise Editions prior to versions 11.5.8, 11.6.6, and 11.7.1.

What type of vulnerability is CVE-2019-6785?

CVE-2019-6785 is classified as a Denial of Service vulnerability caused by overly long string input in Markdown fields.

Is it possible to exploit CVE-2019-6785?

Yes, CVE-2019-6785 can be exploited by inputting excessively long strings into Markdown fields, leading to service interruptions.

Vulnerability/
CVE-2019-6785

medium

6.5

9/9/2019

4/8/2024

CVE-2019-6785

First published: Mon Sep 09 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. It allows Denial of Service. Inputting an overly long string into a Markdown field could cause a denial of service.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=7.4.0<11.5.8
GitLab	>=7.4.0<11.5.8
GitLab	>=11.6.0<11.6.6
GitLab	>=11.6.0<11.6.6
GitLab	>=11.7.0<11.7.1
GitLab	>=11.7.0<11.7.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-6785?
CVE-2019-6785 has a severity rating that indicates it allows for a Denial of Service attack in affected GitLab versions.
How do I fix CVE-2019-6785?
To fix CVE-2019-6785, you should upgrade your GitLab installation to version 11.5.8, 11.6.6, or 11.7.1 or newer.
Which versions are affected by CVE-2019-6785?
CVE-2019-6785 affects GitLab Community and Enterprise Editions prior to versions 11.5.8, 11.6.6, and 11.7.1.
What type of vulnerability is CVE-2019-6785?
CVE-2019-6785 is classified as a Denial of Service vulnerability caused by overly long string input in Markdown fields.
Is it possible to exploit CVE-2019-6785?
Yes, CVE-2019-6785 can be exploited by inputting excessively long strings into Markdown fields, leading to service interruptions.

agent/references
agent/type
agent/author
agent/severity
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/7.4.0
version/gitlab/11.6.0
version/gitlab/11.7.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-6785?
CVE-2019-6785 has a severity rating that indicates it allows for a Denial of Service attack in affected GitLab versions.
How do I fix CVE-2019-6785?
To fix CVE-2019-6785, you should upgrade your GitLab installation to version 11.5.8, 11.6.6, or 11.7.1 or newer.
Which versions are affected by CVE-2019-6785?
CVE-2019-6785 affects GitLab Community and Enterprise Editions prior to versions 11.5.8, 11.6.6, and 11.7.1.
What type of vulnerability is CVE-2019-6785?
CVE-2019-6785 is classified as a Denial of Service vulnerability caused by overly long string input in Markdown fields.
Is it possible to exploit CVE-2019-6785?
Yes, CVE-2019-6785 can be exploited by inputting excessively long strings into Markdown fields, leading to service interruptions.