GitLabApplication
CVE-2018-19580
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 · uneditedAll versions of GitLab prior to 11.5.1, 11.4.8, and 11.3.11 do not send an email to the old email address when an email address change is made.
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 confidenceGitLab versions prior to 11.5.1, 11.4.8, and 11.3.11 have a missing notification feature where changing a user's email address does not trigger a confirmation email to the old email address. This allows account email changes to go unnoticed by the legitimate account owner, potentially enabling account takeover attempts to persist undetected.
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
< 11.3.11>= 11.3.12, < 11.4.8>= 11.4.9, < 11.5.1CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GitLab versionRun `gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` (Omnibus installs) or `cat /home/git/gitlab/VERSION` (source installs)Affected if Version cannot be determined or is not visible
-
Compare version to affected rangesCheck if installed version is: < 11.3.11, OR >= 11.3.12 and < 11.4.8, OR >= 11.4.9 and < 11.5.1Affected if Version falls into any of these ranges indicating the patch is not applied
-
Verify email notification behaviorAs an administrator, attempt a test user email address change through the admin interface and monitor whether a confirmation notification is sent to the old email addressAffected if No confirmation email is sent to the old email address when a user's email is changed (requires admin privileges to test)
-
Check for security fix commitInspect the GitLab source code in `/home/git/gitlab/app/models/user.rb` around the `update_email` method for presence of notification logic to the previous emailAffected if The notification code sending confirmation to the old email address is missing
You are affected if your GitLab version is 11.0.0 through 11.5.0 and the old email address does not receive a confirmation notification when a user's email is changed.
Generated from the published advisory. Verify against your own configuration.
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 data11.3.1111.4.811.5.1
Upgrade GitLab to version 11.5.1, 11.4.8, or 11.3.11 or later to receive the missing email notification to the old address on email changes.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2018-19580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-19580 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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