dbcve.org
GitLabApplication

CVE-2022-4255

MEDIUM · 5.3 CVSS v3.1 Published 2023-01-27
Fix available
A fix is available. Upgrade to 15.4.6 / 15.5.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
An info leak issue was identified in all versions of GitLab EE from 13.7 prior to 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1 which exposes user email id through webhook payload.

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 an information disclosure vulnerability in GitLab EE where user email addresses are inadvertently exposed in webhook payloads. The issue affects multiple versions (13.7 through 15.6) and allows sensitive PII to potentially leak to external systems via configured webhooks.

MitigationUpgrade GitLab EE to version 15.4.6, 15.5.5, or 15.6.1 (or later) to patch the vulnerability. Review existing webhook configurations for any unintended exposure of user email data.

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:>= 13.7.0, < 15.4.6>= 15.5.0, < 15.5.5= 15.6.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Determine installed GitLab version
    Navigate to Admin Area > Dashboard or use the command: sudo gitlab-rake gitlab:env:info. Alternatively, check /opt/gitlab/version or the API endpoint /api/v4/version
    Affected if version falls within 13.7.0 to 15.4.5, 15.5.0 to 15.5.4, or equals 15.6.0
  2. Check for configured webhooks
    Navigate to Admin Area > Webhooks or use the GitLab API: GET /api/v4/hooks. Review the list of webhook endpoints configured in the instance
    Affected if one or more webhooks are configured and the GitLab version is vulnerable
  3. Identify webhooks listening for user-related events
    Examine each webhook URL and check which event types are selected. Look for hooks that include events such as user creation, user update, or member addition
    Affected if webhooks exist that subscribe to user or project_member events and the GitLab version is vulnerable
  4. Review webhook payload contents
    Inspect recent webhook deliveries or test webhooks to observe the JSON payload structure. Specifically look for user email addresses in the payload data
    Affected if webhook payloads contain user email addresses and the GitLab version is vulnerable

You are affected if your GitLab EE version is 13.7.0 through 15.4.5, 15.5.0 through 15.5.4, or exactly 15.6.0 AND you have webhooks configured that could expose user email addresses in their payloads.

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.4.6 / 15.5.5 or later
Fixed in 15.4.615.5.5
Interim mitigation

Upgrade GitLab EE to version 15.4.6, 15.5.5, or 15.6.1 (or later) to patch the vulnerability. Review existing webhook configurations for any unintended exposure of user email data.

Recommended fix High confidence

15.4.6, 15.5.5, or 15.6.1 (or later stable releases in those minor series)

  1. Identify your current GitLab version using the GitLab admin area or `gitlab-rake gitlab:env:info`
  2. Back up your GitLab database and repositories before upgrading
  3. For GitLab 13.7.x through 15.3.x: upgrade to GitLab 15.4.6 or later (recommended: latest 15.4.x stable)
  4. For GitLab 15.4.x (x < 6): upgrade to GitLab 15.4.6 or later
  5. For GitLab 15.5.x (x < 5): upgrade to GitLab 15.5.5 or later
  6. For GitLab 15.6.0: upgrade to GitLab 15.6.1 or later
  7. After upgrade, verify the version using `gitlab-rake gitlab:env:info`
  8. Test webhook functionality to confirm the email leak is remediated
Caveat Patch version upgrades within the same minor series typically have no breaking changes; however, review GitLab release notes for any deprecation notices

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4255 — 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-4255 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