LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0518: An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.0 before 15.6.7, all v...

An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.0 before 15.6.7, all versions starting from 15.7 before 15.7.6, all versions starting from 15.8 before 15.8.1. It was possible to trigger a DoS attack by uploading a malicious Helm chart.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-0518 is a GitLab CE/EE denial-of-service flaw where an authenticated user could upload a malicious Helm chart and reduce availability. It affects GitLab 14.0 through vulnerable 15.8 releases. The public record rates it medium, with no confidentiality or integrity impact stated.

Executive priority

Treat this as a moderate operational resilience issue. It is not described as data theft or code execution, but vulnerable GitLab instances can support critical engineering workflows, so patch during the next controlled maintenance window, sooner for exposed shared services.

Technical view

The issue is classified as CWE-400 resource consumption. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, meaning network reachable, low complexity, requiring low privileges, and affecting availability only. Fixed version boundaries are 15.6.7, 15.7.6, and 15.8.1.

Likely exposure

Exposure is limited to GitLab CE/EE instances in the listed vulnerable ranges where users can upload Helm charts. Internet-facing or broadly accessible GitLab instances have higher operational risk because low-privileged authenticated users may be enough.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. They describe a denial-of-service condition triggered by uploading a malicious Helm chart, but do not provide evidence of exploitation in the wild.

Researcher notes

The source bundle gives clear affected-version and CVSS data but limited implementation detail. Avoid inferring broader package-registry impact beyond malicious Helm chart uploads. No public source in the bundle supports active exploitation or a workaround beyond moving to fixed versions.

Mitigation direction

  • Upgrade GitLab to 15.6.7, 15.7.6, 15.8.1, or a later supported release.
  • Prioritize internet-facing and shared GitLab instances first.
  • Review vendor guidance for any version-specific upgrade notes.
  • Limit Helm chart upload access until upgraded, where business workflows allow.
  • Monitor GitLab availability and package upload activity around suspected incidents.

Validation and detection

  • Inventory GitLab CE/EE versions across self-managed environments.
  • Flag versions >=14.0 and below the fixed release boundaries.
  • Confirm whether Helm chart upload or package registry workflows are enabled.
  • Review recent package upload events for unusual timing or volume.
  • Check availability monitoring for unexplained GitLab degradation.
Prepared
Confidence
high
Sources
5

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.

cwe · low confidence lookup

CWE-400: 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 lookup
cve · low confidence lookup

CVE-2023-0518 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
4.3 (3.1)
Known Exploited
No
Published

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

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
4Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-0518Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
GitLabGitLab>=14.0, <15.6.7, >=15.7, <15.7.6, >=15.8, <15.8.1Listed
Weakness

CWE details

CWE-400

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