GitLab Community Edition/Enterprise Edition up to 11.11.5/12.0.3/12.1.1 Wiki Page Persistent cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in GitLab Community Edition and Enterprise Edition up to 11.11.5/12.0.3/12.1.1. This impacts an unknown function of the component Wiki Page. The manipulation results in cross site scripting (Persistent). This vulnerability is known as CVE-2019-5467. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in GitLab Community Edition and Enterprise Edition up to 11.11.5/12.0.3/12.1.1 (Bug Tracking Software). Affected is an unknown part of the component Wiki Page. The manipulation with an unknown input leads to a cross site scripting vulnerability (Persistent). CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. CVE summarizes:
An input validation and output encoding issue was discovered in the GitLab CE/EE wiki pages feature which could result in a persistent XSS. This vulnerability was addressed in 12.1.2, 12.0.4, and 11.11.6.
The weakness was published 09/09/2019 (Website). The advisory is shared for download at gitlab.com. This vulnerability is traded as CVE-2019-5467 since 01/04/2019. It is possible to launch the attack remotely. A authentication is necessary for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.007.
Upgrading to version 11.11.6, 12.0.4 or 12.1.2 eliminates this vulnerability.
Similar entries are available at VDB-141484, VDB-141482, VDB-141481 and VDB-141479. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: PersistentClass: Cross site scripting / Persistent
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 11.11.6/12.0.4/12.1.2
Timeline
01/04/2019 🔍09/09/2019 🔍
09/10/2019 🔍
12/18/2023 🔍
Sources
Vendor: gitlab.comAdvisory: 60143
Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-5467 (🔍)
GCVE (CVE): GCVE-0-2019-5467
GCVE (VulDB): GCVE-100-141480
See also: 🔍
Entry
Created: 09/10/2019 10:13Updated: 12/18/2023 14:18
Changes: 09/10/2019 10:13 (59), 08/17/2020 16:42 (1), 12/18/2023 14:18 (4)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.