GitLabApplication
CVE-2022-2498
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 issue in pipeline subscriptions in GitLab EE affecting all versions from 12.8 prior to 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1 triggered new pipelines with the person who created the tag as the pipeline creator instead of the subscription's author.
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 confidenceIn GitLab EE, pipeline subscriptions incorrectly attributed newly triggered pipelines to the tag creator rather than the subscription's author. This authorization flaw allowed pipelines to be falsely attributed to users who did not initiate them, potentially enabling privilege escalation through unauthorized pipeline attribution.
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, < 15.0.5>= 15.1.0, < 15.1.4= 15.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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify your GitLab EE versionCheck the installed GitLab version by running `sudo gitlab-rake gitlab:env:info` or looking at the GitLab admin area footer. Compare the version to the affected ranges: 12.8.0 to before 15.0.5, 15.1.0 to before 15.1.4, or exactly 15.2.Affected if The installed version falls within any of these ranges: >=12.8.0 and <15.0.5, >=15.1.0 and <15.1.4, or equals 15.2
-
Confirm pipeline subscriptions are in useNavigate to Project Settings > CI/CD > Pipeline subscriptions in your GitLab instance. Look for any subscriptions where one project receives pipeline events from another project.Affected if There are active pipeline subscriptions configured between projects
-
Inspect recent pipeline attributionReview recent pipelines triggered via subscriptions in your project pipelines list. Check the pipeline details to see which user is listed as the triggerer/author of pipelines that originated from subscribed projects.Affected if Pipelines from subscribed projects show a different user as the triggerer than the actual subscription owner
-
Check for suspicious pipeline attribution patternsExamine the pipeline history for pipelines with unexpected attribution. Look at the user avatar and username shown on pipelines that were triggered through project subscriptions.Affected if Pipelines triggered through subscriptions are attributed to users other than those who created the subscription
You are affected if your GitLab EE version is in the vulnerable range AND you have pipeline subscriptions configured, with pipelines incorrectly attributed to the tag creator instead of the subscription author.
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.
dbcve · scoped15.0.515.1.4
Upgrade GitLab to version 15.0.5, 15.1.4, 15.2.1 or later to patch the pipeline subscription authorization flaw.
15.0.5, 15.1.4, or 15.2.1 (or later in respective branches)
- 1. Identify your current GitLab EE version using the GitLab admin panel or `gitlab-rake gitlab:version`
- 2. If running version >= 12.8.0 and < 15.0.5, plan upgrade to 15.0.5 or later
- 3. If running version >= 15.1.0 and < 15.1.4, plan upgrade to 15.1.4 or later
- 4. If running version 15.2.0, plan upgrade to 15.2.1 or later
- 5. Review GitLab upgrade documentation for your current version to target version
- 6. Perform a full backup of the GitLab database and repositories before upgrading
- 7. Follow the official GitLab upgrade path documentation to upgrade to the chosen fixed version
- 8. After upgrade, verify pipeline subscription functionality works correctly with proper attribution
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2498 — 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-2022-2498 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