dbcve.org
GitLabApplication

CVE-2022-0425

HIGH · 7.6 CVSS v3.1 Published 2022-04-01
Fix available
A fix is available. Upgrade to after 14.7.1 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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
A DNS rebinding vulnerability in the Irker IRC Gateway integration in all versions of GitLab CE/EE since version 7.9 allows an attacker to trigger Server Side Request Forgery (SSRF) attacks.

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 · moderate confidence

A DNS rebinding vulnerability in the Irker IRC Gateway integration in GitLab CE/EE allows attackers to bypass SSRF protections by manipulating DNS records to first resolve to an allowed domain then redirect to internal/infrastructure addresses.

MitigationImplement DNS rebinding protections by validating resolved IP addresses against a denylist of internal/sensitive ranges, using allowlists, and performing DNS resolution checks at request time rather than connection time.

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:>= 7.9.0, <= 14.7.1

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

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

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. Identify GitLab version
    Run 'gitlab-rake gitlab:env:info' or check the GitLab admin panel under Help > Version to retrieve the installed GitLab version
    Affected if The installed version is greater than or equal to 7.9.0 AND less than or equal to 14.7.1
  2. Verify Irker service is configured
    Check GitLab admin settings under System Hooks or Integrations pages for any Irker IRC Gateway configuration, or inspect /etc/gitlab/gitlab.rb for 'irker' settings if using Omnibus installation
    Affected if Irker IRC Gateway integration is enabled or configured in the GitLab instance
  3. Confirm network exposure
    Review the GitLab server's network configuration to determine if the Irker service can receive external requests or is accessible from untrusted networks
    Affected if The GitLab instance is network-accessible from untrusted sources and Irker is enabled
  4. Check for SSRF protection gaps
    Verify whether the Irker configuration uses DNS allowlists without IP validation, or if DNS rebinding protections are documented as not implemented
    Affected if Irker is configured without DNS rebinding protections such as IP denylist validation or real-time DNS resolution checks

You are affected if GitLab version is between 7.9.0 and 14.7.1 inclusive AND the Irker IRC Gateway integration is enabled and accessible, allowing potential DNS rebinding attacks to bypass SSRF protections.

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 a release after 14.7.1
Interim mitigation

Implement DNS rebinding protections by validating resolved IP addresses against a denylist of internal/sensitive ranges, using allowlists, and performing DNS resolution checks at request time rather than connection time.

Recommended fix Moderate confidence

GitLab 14.7.2 or later (recommended: latest stable 14.x release)

  1. 1. Back up your GitLab instance data before proceeding with any upgrade
  2. 2. Identify your current GitLab version by navigating to the GitLab admin area or running `gitlab-rake gitlab:env:info`
  3. 3. Plan your upgrade path based on your current version - if below 14.7.1, you can upgrade directly to 14.7.2 or later
  4. 4. For self-managed installations: stop GitLab services using `gitlab-ctl stop`
  5. 5. Update GitLab using your package manager (e.g., `apt-get update && apt-get install gitlab-ce` or `yum update gitlab-ce`)
  6. 6. Reconfigure GitLab using `gitlab-ctl reconfigure`
  7. 7. Start GitLab services using `gitlab-ctl start`
  8. 8. Verify the upgrade was successful by checking the GitLab version at `https://your-gitlab-instance/admin/about`
Caveat Minor point upgrade - should not introduce breaking changes; however, always review release notes for any noted 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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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