LiveActive security incident?Get immediate response
CVE Record

CVE-2018-20497: An issue was discovered in GitLab Community and Enterprise Edition before 11.4.13, 11.5.x before 11.5.6, an...

An issue was discovered in GitLab Community and Enterprise Edition before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1. It allows SSRF.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-20497 is a server-side request forgery issue in older GitLab Community and Enterprise Edition releases. A vulnerable GitLab server could be induced to make unintended server-side requests. The public bundle identifies fixed version lines but provides no CVSS score, CWE, or confirmed exploitation evidence.

Executive priority

Treat this as a legacy GitLab exposure check. It is not KEV-listed in the provided bundle, but unpatched internet-facing GitLab systems should be remediated because SSRF can create broader internal-network risk.

Technical view

The CVE record states GitLab CE/EE versions before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1 allow SSRF. The bundle does not describe the vulnerable feature, request path, privileges required, or impact beyond SSRF.

Likely exposure

Exposure is most likely on self-managed GitLab CE/EE installations still running the listed 11.4, 11.5, or 11.6 vulnerable versions. Hosted or upgraded instances are not shown as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Because SSRF can affect internal services depending on deployment context, assess urgency higher for internet-facing GitLab instances with sensitive internal network access.

Researcher notes

Evidence is sparse: the CVE states SSRF and affected fixed-version boundaries, but omits CVSS, CWE, vulnerable component detail, exploit preconditions, and full impact. Avoid assumptions beyond GitLab CE/EE version exposure unless vendor issue details are confirmed.

Mitigation direction

  • Upgrade GitLab CE/EE to 11.4.13, 11.5.6, 11.6.1, or later as applicable.
  • Review GitLab’s December 31, 2018 security release guidance.
  • If upgrade timing is constrained, follow vendor guidance for temporary controls.
  • Prioritize internet-facing self-managed GitLab instances first.

Validation and detection

  • Inventory all self-managed GitLab CE/EE instances and recorded versions.
  • Confirm no instance runs before 11.4.13, 11.5.6, or 11.6.1.
  • Check GitLab maintenance records for the December 31, 2018 security update.
  • Document any unsupported or unverified GitLab deployments for remediation tracking.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Cloud 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 lookup
cve · low confidence lookup

CVE-2018-20497 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.