LiveActive security incident?Get immediate response
CVE Record

CVE-2023-1401: Insertion of Sensitive Information Into Sent Data in GitLab

An issue has been discovered in GitLab DAST scanner affecting all versions starting from 3.0.29 before 4.0.5, in which the DAST scanner leak cross site cookies on redirect during authorization.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-1401 is a medium-severity GitLab DAST scanner issue where authorization redirects could cause cross-site cookies to be sent where they should not be. The business risk is limited confidentiality exposure, not system takeover or service disruption, based on the supplied CVSS details.

Executive priority

Treat as a moderate-priority remediation item. Prioritize environments using authenticated DAST scans, because leaked cookies can expose session data, but the sources indicate limited confidentiality impact and no confirmed active exploitation.

Technical view

GitLab reports the DAST scanner is affected from version 3.0.29 before 4.0.5. During authorization redirects, cross-site cookies may leak into sent data. The CVSS vector indicates network reachability, low complexity, low privileges required, no user interaction, changed scope, and low confidentiality impact only.

Likely exposure

Exposure is most likely in GitLab CI/CD environments using affected DAST scanner versions for authenticated web application scans, especially where authorization flows redirect across sites while cookies are present.

Exploitation context

The supplied sources include a public HackerOne report tagged with technical description, exploit, and permissions required. CISA KEV status is false, and the bundle provides no evidence of active exploitation in the wild.

Researcher notes

Focus validation on DAST authorization redirect behavior and whether cross-site cookies appear in outbound requests, logs, or artifacts. Do not assume broader GitLab platform compromise; the supplied record specifically identifies the DAST scanner version range.

Mitigation direction

  • Upgrade GitLab DAST scanner to version 4.0.5 or later.
  • Review GitLab’s issue and advisory context for deployment-specific guidance.
  • Identify authenticated DAST jobs that ran with affected scanner versions.
  • Rotate exposed session cookies or credentials if logs show leakage.
  • Limit scanner credentials to least privilege for future authenticated scans.

Validation and detection

  • Inventory GitLab DAST scanner versions used in CI/CD pipelines.
  • Confirm no jobs use DAST scanner versions 3.0.29 through before 4.0.5.
  • Review affected scan logs and artifacts for unintended cookie disclosure.
  • Check authenticated scan configurations involving redirects across sites.
  • Document findings and remediation status for vulnerability management tracking.
Prepared
Confidence
high
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.

cwe · medium confidence lookup

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

CVE-2023-1401 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.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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
5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N3.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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
GitLabGitLab3.0.29unaffected
Weakness

CWE details

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

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.