What is the severity of CVE-2020-10076?

CVE-2020-10076 is considered a medium severity vulnerability due to its potential impact on users through stored cross-site scripting.

How do I fix CVE-2020-10076?

To fix CVE-2020-10076, you should upgrade GitLab to a version higher than 12.8.1, ideally to the latest release.

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

CVE-2020-10076 affects GitLab versions from 12.1.0 to 12.8.1 for both Community and Enterprise editions.

What kind of attack can exploit CVE-2020-10076?

CVE-2020-10076 can be exploited through stored cross-site scripting attacks targeting users when viewing merge requests.

Is there a workaround for CVE-2020-10076?

There are no known workarounds for CVE-2020-10076; upgrading to a patched version is the recommended solution.

Vulnerability/
CVE-2020-10076

medium

6.1

CWE

13/3/2020

4/8/2024

CVE-2020-10076: XSS

First published: Fri Mar 13 2020(Updated: )

GitLab 12.1 through 12.8.1 allows XSS. A stored cross-site scripting vulnerability was discovered when displaying merge requests.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=12.1.0<=12.8.1
GitLab	>=12.1.0<=12.8.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-10076?
CVE-2020-10076 is considered a medium severity vulnerability due to its potential impact on users through stored cross-site scripting.
How do I fix CVE-2020-10076?
To fix CVE-2020-10076, you should upgrade GitLab to a version higher than 12.8.1, ideally to the latest release.
Which versions of GitLab are affected by CVE-2020-10076?
CVE-2020-10076 affects GitLab versions from 12.1.0 to 12.8.1 for both Community and Enterprise editions.
What kind of attack can exploit CVE-2020-10076?
CVE-2020-10076 can be exploited through stored cross-site scripting attacks targeting users when viewing merge requests.
Is there a workaround for CVE-2020-10076?
There are no known workarounds for CVE-2020-10076; upgrading to a patched version is the recommended solution.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
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.1.0
version/gitlab/12.8.1

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-10076?
CVE-2020-10076 is considered a medium severity vulnerability due to its potential impact on users through stored cross-site scripting.
How do I fix CVE-2020-10076?
To fix CVE-2020-10076, you should upgrade GitLab to a version higher than 12.8.1, ideally to the latest release.
Which versions of GitLab are affected by CVE-2020-10076?
CVE-2020-10076 affects GitLab versions from 12.1.0 to 12.8.1 for both Community and Enterprise editions.
What kind of attack can exploit CVE-2020-10076?
CVE-2020-10076 can be exploited through stored cross-site scripting attacks targeting users when viewing merge requests.
Is there a workaround for CVE-2020-10076?
There are no known workarounds for CVE-2020-10076; upgrading to a patched version is the recommended solution.