LiveActive security incident?Get immediate response
CVE Record

CVE-2018-17453: An issue was discovered in GitLab Community and Enterprise Edition before 11.1.7, 11.2.x before 11.2.4, and...

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. Attackers may have been able to obtain sensitive access-token data from Sentry logs via the GRPC::Unknown exception.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older GitLab Community and Enterprise Edition releases could expose sensitive access-token data into Sentry error logs. The business risk is unauthorized viewing of tokens by anyone with access to those logs, not direct system takeover from the CVE itself.

Executive priority

Prioritize remediation if affected GitLab versions are still running or if Sentry logs are broadly accessible. This is moderate severity because it can expose credentials, but the sources do not indicate integrity loss, availability impact, or active exploitation.

Technical view

GitLab CE/EE before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1 may log access-token data through a GRPC::Unknown exception path into Sentry. CVSS is 5.3, network reachable, low complexity, no privileges or user interaction, confidentiality impact only.

Likely exposure

Exposure is limited to organizations running the affected GitLab versions with Sentry logging capturing the relevant exception data. Systems already upgraded to 11.1.7, 11.2.4, 11.3.1, or later are outside the named vulnerable ranges.

Exploitation context

The provided sources do not show known active exploitation, and CISA KEV is false. The issue concerns sensitive data disclosure through logs; practical impact depends on whether Sentry logs were generated, retained, and accessible to unauthorized or overly broad users.

Researcher notes

Key evidence is the GitLab advisory and CVE description. Affected-version metadata in the bundle is incomplete, but the description names GitLab CE/EE vulnerable ranges. No CWE, exploit evidence, or detailed mitigation beyond fixed versions is provided.

Mitigation direction

  • Upgrade GitLab to 11.1.7, 11.2.4, 11.3.1, or later.
  • Review GitLab’s security release notes for version-specific guidance.
  • Restrict access to Sentry logs containing GitLab exceptions.
  • If tokens are found in logs, follow credential rotation procedures.

Validation and detection

  • Inventory GitLab CE/EE versions against the affected release ranges.
  • Confirm deployed GitLab version is at or above the fixed release.
  • Review Sentry logs for GitLab GRPC::Unknown exceptions during the exposure window.
  • Check whether access-token values appeared in retained Sentry records.
Prepared
Confidence
high
Sources
4

Public sources used

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

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

CVE-2018-17453 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2018-17453Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

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.