dbcve.org
GitLabApplication

CVE-2022-2428

HIGH · 7.3 CVSS v3.1 Published 2022-10-17
Fix available
A fix is available. Upgrade to 15.1.6 / 15.2.4 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable

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 · unedited
A crafted tag in the Jupyter Notebook viewer in GitLab EE/CE affecting all versions before 15.1.6, 15.2 to 15.2.4, and 15.3 to 15.3.2 allows an attacker to issue arbitrary HTTP requests

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 confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in GitLab's Jupyter Notebook viewer. An attacker can embed a crafted tag within a notebook viewed through GitLab, causing the GitLab server to issue arbitrary HTTP requests to internal or external resources. This could allow enumeration of internal services, access to metadata endpoints, or pivoting to internal infrastructure.

MitigationUpgrade GitLab to version 15.1.6 or later, 15.2.5 or later, or 15.3.3 or later. If immediate upgrade is not possible, consider restricting access to the Jupyter Notebook viewer feature or implementing WAF rules to detect SSRF patterns.

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
Affected:< 15.1.6>= 15.2, < 15.2.4>= 15.3, < 15.3.2

CVSS 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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to find the exact version number
    Affected if Version is 15.0.x, 15.1.0 through 15.1.5, 15.2.0 through 15.2.3, or 15.3.0 through 15.3.1 (these fall within the affected ranges < 15.1.6, >= 15.2 < 15.2.4, or >= 15.3 < 15.3.2)
  2. Confirm Jupyter Notebook viewer is enabled
    Navigate to GitLab admin area > Settings > Repository > expand "Jupyter Notebook viewer" settings, or check gitlab.yml configuration file for `jupyter_notifications_enabled` or similar flags
    Affected if Jupyter Notebook viewer feature is enabled in the GitLab settings, as this is the vulnerable component that processes notebook files
  3. Identify if any notebooks exist in repositories
    Search GitLab repositories for .ipynb files using the API (`GET /search?scope=blobs&search=.ipynb`) or repository browsing UI
    Affected if Repositories contain Jupyter notebook (.ipynb) files that could be viewed through the vulnerable viewer, providing an attack vector

You are affected if your GitLab version falls within the vulnerable ranges AND the Jupyter Notebook viewer feature is enabled and accessible to users with repository view permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 15.1.6 / 15.2.4 / 15.3.2 or later
Fixed in 15.1.615.2.415.3.2
Interim mitigation

Upgrade GitLab to version 15.1.6 or later, 15.2.5 or later, or 15.3.3 or later. If immediate upgrade is not possible, consider restricting access to the Jupyter Notebook viewer feature or implementing WAF rules to detect SSRF patterns.

Recommended fix High confidence

15.1.6, 15.2.4, or 15.3.2 (depending on which branch you are on)

  1. 1. Identify the current GitLab version by running `gitlab-rake gitlab:env:info` or checking the Admin Area dashboard
  2. 2. Based on current version, upgrade to the appropriate fixed release: If < 15.1.6, upgrade to 15.1.6; If >= 15.2.x and < 15.2.4, upgrade to 15.2.4; If >= 15.3.x and < 15.3.2, upgrade to 15.3.2
  3. 3. Follow standard GitLab upgrade procedure using GitLab package manager or source installation method
  4. 4. After upgrade, verify the Jupyter Notebook viewer functionality works correctly
  5. 5. Test that the XSS vulnerability is patched by attempting to load a notebook with crafted script tags - it should not execute
Caveat Point releases typically have minimal breaking changes; review GitLab release notes for specific changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2428 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2428 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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