dbcve.org
GitLabApplication

CVE-2022-1188

MEDIUM · 5.3 CVSS v3.1 Published 2022-04-04
Fix available
A fix is available. Upgrade to 14.7.7 / 14.8.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 issue has been discovered in GitLab CE/EE affecting all versions starting from 12.1 before 14.7.7, all versions starting from 14.8 before 14.8.5, all versions starting from 14.9 before 14.9.2 where a blind SSRF attack through the repository mirroring feature was possible.

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

A blind Server-Side Request Forgery (SSRF) vulnerability in GitLab's repository mirroring feature allows an attacker to induce the server to make arbitrary HTTP requests to internal services or external targets without seeing the response, potentially exposing internal infrastructure.

MitigationUpgrade GitLab to version 14.7.7, 14.9.2, or 14.8.5 or later. If immediate upgrade is not feasible, consider disabling or restricting the repository mirroring feature and implementing network segmentation to limit internal service exposure.

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:>= 12.1.0, < 14.7.7>= 14.8.0, < 14.8.5>= 14.9.0, < 14.9.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
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. Check your GitLab version
    Locate the installed GitLab version by accessing the GitLab Admin Dashboard (usually at /admin) or running `gitlab-rake gitlab:env:info` on the GitLab server. Compare this version against the affected ranges: 12.1.0 to 14.7.6, 14.8.0 to 14.8.4, or 14.9.0 to 14.9.1.
    Affected if Your installed version falls within any of these ranges: >= 12.1.0 and < 14.7.7, >= 14.8.0 and < 14.8.5, or >= 14.9.0 and < 14.9.2.
  2. Verify repository mirroring is enabled
    Navigate to the GitLab Admin area, go to Settings > Repository Mirroring, or check the instance-wide mirroring settings. Alternatively, if you have server access, check the gitlab.yml configuration file for mirroring-related settings.
    Affected if Repository mirroring is enabled at the instance level or project level.
  3. Identify configured repository mirrors
    Check for existing mirror configurations by visiting the repository mirroring page on individual projects (Project Settings > Repository > Mirroring repositories) or querying the database for mirrors using `sudo gitlab-rails console` and running `ProjectMirror.all` or similar queries.
    Affected if Any repository mirrors are configured, especially those pointing to internal or localhost URLs.
  4. Review mirror push settings
    Examine the push mirror settings in the GitLab interface or database to see if any mirrors are configured that could be manipulated to trigger SSRF requests.
    Affected if Push mirrors are configured and the attacker could influence the mirror URL to point to internal services.

You are affected if your GitLab version is within the vulnerable ranges AND repository mirroring is enabled or configured on your instance.

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 14.7.7 / 14.8.5 / 14.9.2 or later
Fixed in 14.7.714.8.514.9.2
Interim mitigation

Upgrade GitLab to version 14.7.7, 14.9.2, or 14.8.5 or later. If immediate upgrade is not feasible, consider disabling or restricting the repository mirroring feature and implementing network segmentation to limit internal service exposure.

Recommended fix High confidence

GitLab 14.9.2 or later (recommended: latest stable 15.x or 16.x release)

  1. 1. Back up your GitLab instance data before proceeding with the upgrade.
  2. 2. Review the GitLab upgrade documentation for your current version to ensure a compatible upgrade path.
  3. 3. Upgrade GitLab to version 14.9.2 or later. For the best security posture, consider upgrading to the latest stable GitLab release (currently 15.x or newer) rather than the minimum fixed version.
  4. 4. After upgrade, verify the repository mirroring feature functions correctly.
  5. 5. Confirm the SSRF vulnerability is resolved by testing that repository mirroring only connects to intended external hosts.
Caveat GitLab minor version upgrades may require database migrations; review release notes for any required pre-upgrade steps and ensure compatibility with your infrastructure

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-1188 — 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-1188 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