GitLab Community Edition/Enterprise Edition up to 11.1.6/11.2.3/11.3.0 Slash Command cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in GitLab Community Edition and Enterprise Edition up to 11.1.6/11.2.3/11.3.0. Affected is an unknown function of the component Slash Command Handler. Performing a manipulation results in cross-site request forgery. This vulnerability is reported as CVE-2018-17451. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in GitLab Community Edition and Enterprise Edition up to 11.1.6/11.2.3/11.3.0 (Bug Tracking Software). This affects some unknown functionality of the component Slash Command Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:
An issue was discovered in GitLab Community and Enterprise Edition before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. There is Cross Site Request Forgery (CSRF) in the Slack integration for issuing slash commands.
The weakness was disclosed 04/16/2023. The advisory is shared at about.gitlab.com. This vulnerability is uniquely identified as CVE-2018-17451 since 09/25/2018. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 11.1.7, 11.2.4 or 11.3.1 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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.1.7/11.2.4/11.3.1
Timeline
09/25/2018 🔍04/16/2023 🔍
04/16/2023 🔍
05/05/2023 🔍
Sources
Vendor: gitlab.comAdvisory: about.gitlab.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-17451 (🔍)
GCVE (CVE): GCVE-0-2018-17451
GCVE (VulDB): GCVE-100-226137
Entry
Created: 04/16/2023 07:52Updated: 05/05/2023 12:15
Changes: 04/16/2023 07:52 (43), 05/05/2023 12:15 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.