GitLabApplication
CVE-2020-10535
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 · uneditedGitLab 12.8.x before 12.8.6, when sign-up is enabled, allows remote attackers to bypass email domain restrictions within the two-day grace period for an unconfirmed email address.
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 12.8.x before 12.8.6 contain an authentication bypass vulnerability where email domain restrictions can be circumvented during a two-day grace period for unconfirmed email addresses when user sign-up is enabled. An attacker could register with a restricted domain email and bypass domain whitelist/blacklist controls within this window.
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
>= 12.8.0, < 12.8.6CVSS 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.1/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.
-
Check installed GitLab versionAccess the GitLab admin area (Admin Area > Overview > Dashboard) or use the API endpoint /api/v4/version to retrieve the running version numberAffected if The version is 12.8.0, 12.8.1, 12.8.2, 12.8.3, 12.8.4, or 12.8.5 (any version >= 12.8.0 and < 12.8.6)
-
Verify user sign-up is enabledNavigate to Admin Area > Settings > General > Sign-up restrictions, or query the application settings API to confirm that sign-up is allowedAffected if Sign-up is enabled (any setting that permits new user registration)
-
Confirm email domain restrictions are configuredNavigate to Admin Area > Settings > General > Sign-up restrictions and check if an email domain blacklist or whitelist is definedAffected if Email domain restrictions (whitelist or blacklist) are configured and enforced
-
Review recent user registrations for suspicious domainsAccess Admin Area > Users and examine newly created accounts within the past 48-72 hours. Check if any accounts were registered with email addresses from domains that should be blocked by your restrictionsAffected if New user accounts exist with email addresses from domains that should be blocked by your configured restrictions
Your environment is affected if you are running GitLab 12.8.0-12.8.5 with sign-ups enabled and email domain restrictions configured, as attackers could have registered with restricted domain addresses during the two-day grace period.
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 data12.8.6
Upgrade to GitLab 12.8.6 or later. If immediate upgrade is not possible, consider disabling sign-ups or implementing additional monitoring for suspicious registration patterns during the grace period.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10535 — 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-2020-10535 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