GitLab Community Edition/Enterprise Edition up to 13.0.1 Blobs API Stored cross site scripting

Summaryinfo

A vulnerability identified as problematic has been detected in GitLab Community Edition and Enterprise Edition up to 13.0.1. Affected by this issue is some unknown functionality of the component Blobs API. This manipulation causes cross site scripting (Stored). This vulnerability is tracked as CVE-2020-13271. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in GitLab Community Edition and Enterprise Edition up to 13.0.1 (Bug Tracking Software) and classified as problematic. Affected by this vulnerability is some unknown functionality of the component Blobs API. The manipulation with an unknown input leads to a cross site scripting vulnerability (Stored). The CWE definition for the vulnerability is CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. As an impact it is known to affect integrity. The summary by CVE is:

A Stored Cross-Site Scripting vulnerability allowed the execution of arbitrary Javascript code in the blobs API in all previous GitLab CE/EE versions through 13.0.1

The weakness was disclosed 06/10/2020 (Website). It is possible to read the advisory at gitlab.com. This vulnerability is known as CVE-2020-13271 since 05/21/2020. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 257891 (Linux Distros Unpatched Vulnerability : CVE-2020-13271), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (257891). The entries VDB-156486, VDB-156485, VDB-156484 and VDB-156483 are pretty similar. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Community Edition
• Enterprise Edition

Version

• 13.0.0
• 13.0.1

License

• open-source

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion