GitLabApplication
CVE-2023-0042
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue has been discovered in GitLab CE/EE affecting all versions starting from 11.4 prior to 15.5.7, 15.6 prior to 15.6.4, and 15.7 prior to 15.7.2. GitLab Pages allows redirection to arbitrary protocols.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGitLab Pages contains an open redirect vulnerability that allows redirection to arbitrary protocols (such as javascript:, data:, or other potentially dangerous URL schemes). This occurs due to insufficient validation of redirect URLs in the Pages feature, enabling attackers to craft malicious redirects for phishing or bypass security controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
>= 11.4.0, < 15.5.7>= 15.6.0, < 15.6.4>= 15.7.0, < 15.7.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed GitLab versionRun `cat /opt/gitlab/version` or execute `gitlab-rake gitlab:env:info` to retrieve the running GitLab versionAffected if Version falls within 11.4.0 to 15.5.6, 15.6.0 to 15.6.3, or 15.7.0 to 15.7.1
-
Verify GitLab Pages is enabledCheck the GitLab configuration file at `/etc/gitlab/gitlab.rb` for the line `pages_external_url` or run `gitlab-ctl status` to see if the Pages service is runningAffected if Pages is enabled via `pages_external_url` directive or the Pages service is active
-
Confirm Pages external URL configurationInspect the `pages_external_url` setting in `/etc/gitlab/gitlab.rb` to identify the configured external URL for PagesAffected if An external URL is configured and the version is in the affected ranges listed above
Your environment is affected if GitLab version is 11.4.0 to 15.5.6, 15.6.0 to 15.6.3, or 15.7.0 to 15.7.1 AND GitLab Pages is enabled with an external URL configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.5.715.6.415.7.2
Upgrade GitLab to version 15.5.7, 15.6.4, or 15.7.2 or later. If GitLab Pages is not required in the environment, it can be disabled as a compensating control.
15.5.7, 15.6.4, or 15.7.2 (or later)
- Identify your current GitLab version using the GitLab Rails console: `Gitlab::VERSION` or the Admin Area > Settings > General page
- Stop GitLab services using: `sudo gitlab-ctl stop`
- Backup your GitLab installation and database
- Update your package repository and install the new package
- For Debian/Ubuntu: `sudo apt-get update` and `sudo apt-get install gitlab-ee` or `gitlab-ce`
- For RHEL/CentOS: `sudo yum install gitlab-ee` or `gitlab-ce`
- Reconfigure GitLab: `sudo gitctl reconfigure`
- Start GitLab services: `sudo gitctl start`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0042 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0042 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data