dbcve.org
GitLabApplication

CVE-2025-1072

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-07
Fix available
A fix is available. Upgrade to 17.3.7 / 17.4.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Denial of Service (DoS) issue has been discovered in GitLab CE/EE affecting all versions starting from 7.14.1 prior to 17.3.7, 17.4 prior to 17.4.4, and 17.5 prior to 17.5.2. A denial of service could occur upon importing maliciously crafted content using the Fogbugz importer.

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 denial of service vulnerability exists in GitLab CE/EE's Fogbugz importer. An attacker can import maliciously crafted content that causes the GitLab instance to become unavailable, likely through resource exhaustion or processing failure.

MitigationUpgrade GitLab to version 17.3.7, 17.4.4, or 17.5.2 or later to remediate this vulnerability. Until then, restrict or disable the Fogbugz import functionality.

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.14.1, < 17.3.7>= 17.4.0, < 17.4.4>= 17.5.0, < 17.5.2>= 17.7.0, < 17.7.3

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Determine installed GitLab version
    Access the GitLab administration interface, go to Admin Area > Settings > General, or use the command line: sudo gitlab-rake gitlab:env:info or check /opt/gitlab/version for omnibus installations
    Affected if The installed version falls within any of these ranges: 7.14.1 to 17.3.6, 17.4.0 to 17.4.3, 17.5.0 to 17.5.1, or 17.7.0 to 17.7.2
  2. Verify Fogbugz import feature is accessible
    Navigate to the user project import page or check via API endpoint /import_exports/status to see available importers, or inspect Admin Area > Settings > General > Import and export for enabled import sources
    Affected if Fogbugz is listed as an available import source and users can initiate a Fogbugz import
  3. Confirm import functionality is not restricted
    Check GitLab configuration files (gitlab.rb or gitlab.yml) for import service restrictions, or verify in Admin Area > Settings > General that import features are not explicitly disabled
    Affected if The Fogbugz importer is not disabled through import_source_restrictions or feature flags

A GitLab instance is affected if it runs a version in the vulnerable ranges AND the Fogbugz import feature remains enabled and accessible to users.

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 17.3.7 / 17.4.4 / 17.5.2 or later
Fixed in 17.3.717.4.417.5.2
Interim mitigation

Upgrade GitLab to version 17.3.7, 17.4.4, or 17.5.2 or later to remediate this vulnerability. Until then, restrict or disable the Fogbugz import functionality.

Recommended fix High confidence

17.3.7, 17.4.4, 17.5.2, or 17.7.3 (depending on your current branch); preferably 17.7.3 or later

  1. 1. Identify the currently installed GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin interface.
  2. 2. Determine which version branch your current installation belongs to (17.3.x, 17.4.x, 17.5.x, or 17.7.x).
  3. 3. For GitLab installations using Omnibus packages: Run `sudo apt-get update && sudo apt-get install gitlab-ce=<version>` (Debian/Ubuntu) or `sudo yum install gitlab-ce-<version>` (RHEL/CentOS), replacing <version> with 17.3.7, 17.4.4, 17.5.2, or 17.7.3 respectively.
  4. 4. For source installations: Navigate to the GitLab source directory and checkout the appropriate tag using `git checkout <version>` where version is one of the fixed releases, then run bundle install and restart GitLab.
  5. 5. After upgrade, verify the GitLab instance is operational by running `sudo gitlab-rake gitlab:check`.
  6. 6. Alternatively, if possible, upgrade to the latest stable version (17.7.x or later) which contains all security fixes.
Caveat Standard GitLab upgrade considerations apply: backup your database and Git repositories before upgrading, review the upgrade path for any required intermediate steps, and test in a staging environment first

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-2025-1072 — 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-2025-1072 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