Security readout for executives and security teams
Plain-English summary
This flaw can let a crafted diff formatting workload tie up GitLab background processing for a long time. The documented impact is availability loss, not data theft or modification. GitLab Community and Enterprise Edition versions before the listed fixed releases are the relevant concern.
Executive priority
Treat this as a high-priority availability risk for older GitLab deployments. It is not documented here as a confidentiality breach, but disruption to source control and CI workflows can directly affect engineering delivery and incident response.
Technical view
CVE-2018-15472 affects GitLab CE/EE before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. The Rouge-based diff formatter could run too long in Sidekiq jobs without a timeout. CVSS 3.1 scores it 7.5, network reachable, no privileges, no user interaction, availability impact only.
Likely exposure
Exposure is most likely where GitLab CE/EE instances remain on vulnerable 11.1, 11.2, or 11.3 release lines. The supplied affected CPE data is not populated, so inventory should rely on actual GitLab version checks rather than CPE matching alone.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates remote, unauthenticated availability impact, but the provided sources do not describe real-world exploitation, exploit maturity, or operational indicators.
Researcher notes
The weakness maps to CWE-770, resource allocation without proper limits. The key behavior is unbounded or long-running Rouge diff formatting inside Sidekiq jobs. Public source detail is limited, so avoid assuming affected inputs, exploit reliability, or fixes beyond the named GitLab versions.
Mitigation direction
- Upgrade GitLab CE/EE to 11.1.7, 11.2.4, 11.3.1, or later fixed releases.
- Prioritize unsupported or internet-facing GitLab instances for version review.
- Monitor GitLab vendor security guidance for any additional remediation details.
- Review Sidekiq capacity and job timeout controls according to vendor-supported configuration.
Validation and detection
- Inventory all GitLab CE/EE instances and record exact versions.
- Flag versions before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1.
- Check Sidekiq logs for unusually long diff formatting jobs or availability degradation.
- Confirm remediation by rechecking the GitLab version after upgrade.
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-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-15472 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
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.