dbcve.org
GitLabApplication

CVE-2019-7353

CRITICAL · 9.1 CVSS v3.0 Published 2019-05-17
Fix available
A fix is available. Upgrade to 11.7.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Incorrect Access Control issue was discovered in GitLab Community and Enterprise Edition 11.7.x before 11.7.4. GitLab Releases were vulnerable to an authorization issue that allowed users to view confidential issue and merge request titles of other projects.

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

GitLab 11.7.x before 11.7.4 contains an incorrect access control vulnerability in the Releases feature that allows authenticated users to view confidential issue and merge request titles from other projects they should not have access to.

MitigationUpgrade GitLab to version 11.7.4 or later to remediate this authorization bypass vulnerability.

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:>= 11.7.0, < 11.7.4

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Identify installed GitLab version
    Run command: `cat /opt/gitlab/version` or check the GitLab admin panel under Help > Version. Alternatively, query the API: `curl -s https://your-gitlab-instance/api/v4/version`
    Affected if The version is 11.7.0, 11.7.1, 11.7.2, or 11.7.3 (any version >= 11.7.0 and < 11.7.4)
  2. Confirm GitLab instance is accessible to external authenticated users
    Review user authentication settings in Admin Area > Settings > General > Sign-up restrictions and Visibility and access controls. Check if self-registration is enabled or if external users are provisioned.
    Affected if Users outside your trusted user base can authenticate to the GitLab instance
  3. Identify projects with confidential issues or merge requests
    Navigate to each project and check Issues > List view. Look for issues marked with a lock icon (confidential). Also review merge requests in the project.
    Affected if Projects contain confidential issues or merge requests that should not be visible to all authenticated users
  4. Verify cross-project user access permissions
    Review which users have access to which projects in Admin Area > Users > Projects tab. Check for users who have access to Project A but should NOT have access to Project B that contains confidential content.
    Affected if There are users who have access to some projects but not others, and those users could access the Releases feature of projects they should not access

You are affected if your GitLab version is 11.7.0 through 11.7.3, you have authenticated users who should not see all project content, and your instance uses the Releases feature with projects containing confidential issues or merge requests.

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 11.7.4 or later
Fixed in 11.7.4
Interim mitigation

Upgrade GitLab to version 11.7.4 or later to remediate this authorization bypass vulnerability.

Recommended fix High confidence

GitLab 11.7.4

  1. Back up your GitLab instance data and database before upgrading
  2. Update your GitLab package to version 11.7.4 or later
  3. For Omnibus installations: run 'gitlab-ctl reconfigure' after the package update
  4. For source installations: follow the standard upgrade procedure in the GitLab documentation
  5. Verify the upgrade was successful by checking GitLab is operational
  6. Confirm the access control issue is resolved by testing that users cannot access confidential issue/MR titles from other projects

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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