Security readout for executives and security teams
Plain-English summary
This GitLab issue let a malicious site abuse a logged-in user's browser to send unauthorized Slack slash-command integration requests. The risk depends on running vulnerable GitLab CE/EE versions and using the Slack integration. Impact is rated high because successful CSRF could affect confidentiality, integrity, and availability.
Executive priority
Treat as a high-priority maintenance fix for any vulnerable GitLab instance using Slack slash commands. Prioritize internet-facing or broadly used GitLab deployments first.
Technical view
CVE-2018-17451 is CWE-352 CSRF in GitLab Community and Enterprise Edition Slack integration slash commands. Affected versions are before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Likely exposed assets are self-managed GitLab CE/EE instances in the listed vulnerable version ranges where Slack integration slash commands are enabled.
Exploitation context
The provided sources do not show active exploitation, and this CVE is not listed as KEV. The CVSS vector indicates exploitation requires user interaction but no attacker privileges.
Researcher notes
The CVE affected-product metadata is incomplete, but the description names GitLab CE/EE and fixed version boundaries. Sources do not provide endpoint details, exploit evidence, or separate mitigations beyond the GitLab security release context.
Mitigation direction
- Upgrade GitLab CE/EE to 11.1.7, 11.2.4, 11.3.1, or later.
- Review GitLab's security release for version-specific upgrade guidance.
- Inventory Slack integration slash-command usage on affected GitLab instances.
- If upgrade is delayed, check GitLab guidance before relying on compensating controls.
Validation and detection
- Identify all self-managed GitLab CE/EE instances and installed versions.
- Flag versions before 11.1.7, 11.2.4, or 11.3.1 as affected.
- Confirm whether Slack integration slash commands are configured.
- Verify the installed version matches a fixed release or later.
- Review change records for completion of the relevant GitLab security update.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2018-17451 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.