Security readout for executives and security teams
Plain-English summary
CVE-2018-17450 is an SSRF flaw in older GitLab Community and Enterprise Edition releases. A logged-in attacker could abuse the Kubernetes integration to make GitLab request internal resources, with token disclosure cited as an example. Business urgency is moderate, especially for GitLab instances connected to Kubernetes or Google Cloud.
Executive priority
Treat as a moderate remediation item. Prioritize internet-accessible or cloud-integrated GitLab systems, because the business risk is credential exposure rather than broad system takeover. Absence from KEV lowers urgency, but affected production instances should still be upgraded promptly.
Technical view
The flaw is CWE-918 SSRF in GitLab CE/EE before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, low confidentiality impact, no integrity or availability impact stated.
Likely exposure
Exposure is most relevant to self-managed GitLab CE/EE instances running the affected version ranges with Kubernetes integration configured. The source bundle does not identify affected CPEs or cloud deployment specifics, so teams should validate actual GitLab version and integration usage rather than assuming exposure.
Exploitation context
The CVE is not listed as KEV in the provided data, and the source bundle does not cite active exploitation. Exploitation requires at least low privileges. Impact centers on unauthorized server-side requests and possible disclosure of sensitive cloud service tokens, including the cited GCP service token example.
Researcher notes
The public data supports SSRF through the Kubernetes integration and possible GCP token disclosure, but does not provide detailed exploit conditions, affected CPEs, or observed exploitation. Validation should focus on version range, enabled integration paths, cloud token exposure, and confirmation that fixed GitLab releases are deployed.
Mitigation direction
- Upgrade GitLab CE/EE to 11.1.7, 11.2.4, 11.3.1, or later supported releases.
- Review GitLab's 2018-10-01 security release guidance for the fixed release path.
- Audit Kubernetes integration settings on any affected GitLab instance.
- Review exposed cloud service tokens and rotate any credentials suspected of disclosure.
Validation and detection
- Inventory all self-managed GitLab CE/EE versions.
- Identify instances in the affected version ranges.
- Confirm whether Kubernetes integration is enabled on those instances.
- Verify upgrade status against fixed GitLab releases.
- Review logs and cloud audit trails for unexpected metadata or token access.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-17450 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.