RundeckApplication · Jenkins
CVE-2022-30956
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 Rundeck Plugin 3.6.10 and earlier does not restrict URL schemes in Rundeck webhook submissions, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to submit crafted Rundeck webhook payloads.
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 confidenceThe Jenkins Rundeck Plugin versions 3.6.10 and earlier fail to restrict URL schemes in Rundeck webhook submissions, allowing attackers to inject malicious JavaScript or HTML payloads that execute when the webhook data is rendered. This stored XSS vulnerability stems from missing input validation on the webhook endpoint.
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
RundeckApplication
<= 3.6.10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 the Rundeck Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and locate the Rundeck Plugin in the list to see its version number. Alternatively, use the Jenkins CLI: jenkins-plugin-cli --list-plugins | grep rundeckAffected if The displayed version is 3.6.10 or earlier
-
Verify if webhooks are configuredCheck your Jenkins jobs for any Rundeck webhook triggers or callback endpoints. This is typically found in job configuration pages under Build Triggers or in the Rundeck plugin global configuration if webhook URLs have been generated.Affected if Any Jenkins job has a Rundeck webhook URL configured or active, meaning external parties can submit data to that endpoint
-
Confirm webhook submission is possibleAttempt to access or inspect the Rundeck webhook endpoint URL pattern (typically /rundeck-webhook/ or similar under your Jenkins root URL) to verify it is accessible and accepts POST requests.Affected if The webhook endpoint is reachable without authentication barriers and accepts arbitrary payload data
You are affected if the Rundeck Plugin version is 3.6.10 or earlier AND any Rundeck webhook endpoint is exposed and accessible in your Jenkins environment.
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 the Rundeck Plugin to version 3.6.11 or later which includes URL scheme validation. As a compensating control, restrict Rundeck webhook permissions to trusted users only until the patch is applied.
Rundeck Plugin version 3.6.11 or later
- 1. Navigate to the Jenkins dashboard
- 2. Go to Manage Jenkins > Manage Plugins
- 3. Select the 'Installed' tab
- 4. Find the Rundeck Plugin in the list
- 5. If an update is available, click 'Update' to upgrade to the fixed version
- 6. Restart Jenkins to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rundeck
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30956 — 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-30956 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