dbcve.org
GitLabApplication

CVE-2019-15738

MEDIUM · 5.3 CVSS v3.1 Published 2019-09-16
Fix available
A fix is available. Upgrade to 12.0.8 / 12.1.8 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 was discovered in GitLab Community and Enterprise Edition 12.0 through 12.2.1. Under certain conditions, merge request IDs were being disclosed via email.

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

GitLab versions 12.0 through 12.2.1 had a flaw where merge request IDs could be disclosed via email under certain conditions. This represents an information disclosure vulnerability where sensitive internal identifiers are exposed to unauthorized parties through the email notification system.

MitigationUpgrade GitLab to version 12.2.2 or later. As a precaution, review email logs and notifications sent during the affected versions to determine if any merge request IDs were inadvertently disclosed.

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.0.0, < 12.0.8>= 12.1.0, < 12.1.8>= 12.2.0, < 12.2.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
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
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under the Help > Versions page
    Affected if Version is 12.0.0-12.0.7, 12.1.0-12.1.7, or 12.2.0-12.2.2 (falls within affected ranges)
  2. Verify email notifications are enabled
    Check GitLab settings at Admin Area > Settings > Emails > Email notifications is enabled, or review /etc/gitlab/gitlab.rb for `gitlab_rails['gitlab_email_enabled']`
    Affected if Email notifications are enabled and the GitLab version is within affected ranges

Environment is affected if GitLab version is 12.0.0-12.0.7, 12.1.0-12.1.7, or 12.2.0-12.2.2 and email notifications are configured.

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.

From vendor data
Upgrade available Upgrade to 12.0.8 / 12.1.8 / 12.2.3 or later
Fixed in 12.0.812.1.812.2.3
Interim mitigation

Upgrade GitLab to version 12.2.2 or later. As a precaution, review email logs and notifications sent during the affected versions to determine if any merge request IDs were inadvertently disclosed.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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