GitLabApplication
CVE-2019-15582
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 · uneditedAn IDOR was discovered in < 12.3.2, < 12.2.6, and < 12.1.12 for GitLab Community Edition (CE) and Enterprise Edition (EE) that allowed a maintainer to add any private group to a protected environment.
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 confidenceAn IDOR vulnerability in GitLab versions prior to 12.1.12, 12.2.6, and 12.3.2 allowed a maintainer user to add any private group to a protected environment, bypassing proper authorization checks. The application failed to validate that the maintainer only had access to groups they legitimately controlled.
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.1.0, < 12.1.12>= 12.2.0, < 12.2.6>= 12.3.0, < 12.3.2CVSS 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.
-
Determine your GitLab versionLog in as an administrator and go to Admin Area > Settings > General, or query the API endpoint /api/v4/version. The version is displayed at the bottom of the Admin dashboard sidebar.Affected if The installed version is 12.1.0 to 12.1.11, 12.2.0 to 12.2.5, or 12.3.0 to 12.3.1.
-
Verify protected environments are in useNavigate to a project repository, go to Settings > CI/CD, and expand the Protected environments section. Alternatively, query the GitLab API: GET /projects/:id/protected_environments.Affected if Any protected environments are defined in the GitLab instance.
-
Check group deployment access rulesIn the protected environments settings, review any access rules that grant deployment access to groups. Note the group names and membership.Affected if Deployment access rules include groups that maintainers should not have authorization to add.
-
Audit recent environment protection changesUse the UI: go to Project > Repository > Commits > Audit Events, or check the audit logs via the API for events of type protected_environment_update. Look for additions of unfamiliar groups.Affected if Audit logs show group additions to protected environments made by users who do not own or administer those groups.
You are affected if your GitLab version is within the vulnerable range AND protected environments with group access rules exist, particularly if unauthorized groups appear in deployment access rules.
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.1.1212.2.612.3.2
Upgrade GitLab to version 12.3.2, 12.2.6, or 12.1.12 or later to receive the patch that adds proper authorization validation when adding groups to protected environments.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15582 — 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-2019-15582 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