GitLabApplication · Jenkins
CVE-2022-30955
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 · uneditedJenkins GitLab Plugin 1.5.31 and earlier does not perform a permission check in an HTTP endpoint, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
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 confidenceJenkins GitLab Plugin versions 1.5.31 and earlier contain an HTTP endpoint that lacks proper permission validation, allowing any authenticated user with Overall/Read permission (a low-privilege role) to enumerate credential IDs stored in Jenkins' internal credentials store. This exposes credential identifiers that could facilitate further attacks targeting those credentials.
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
<= 1.5.31CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check GitLab Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed, locate GitLab Plugin in the list, and record the installed version numberAffected if Version is 1.5.31 or earlier
-
Verify credentials exist in JenkinsNavigate to Manage Jenkins > Manage Credentials and inspect whether any credentials are stored in any domainAffected if Any credentials are present in Jenkins' internal credentials store
-
Identify authenticated users with low privilegesNavigate to Manage Jenkins > Manage Users and review user accounts; also check Jenkins security realm for users that could authenticate with Overall/Read permissionAffected if Any authenticated user account exists in Jenkins (beyond just administrators)
Environment is affected if the GitLab Plugin version is 1.5.31 or earlier AND credentials are stored in Jenkins AND at least one authenticated user with basic read access exists in the system.
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 · scopedUpgrade Jenkins GitLab Plugin to version 1.5.32 or later, which implements proper permission checks on the affected HTTP endpoint.
GitLab Plugin version > 1.5.31 (check Jenkins Plugin Repository for latest stable version)
- Navigate to the Jenkins dashboard
- Go to Manage Jenkins > Manage Plugins
- Click on the 'Installed' tab
- Locate the 'GitLab Plugin' in the list
- If an update is available, select the GitLab Plugin and click 'Download now and install after restart'
- Wait for the plugin to update to a version newer than 1.5.31
- Restart Jenkins to apply the changes
- Verify the plugin version is greater than 1.5.31
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30955 — 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-30955 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