dbcve.org
RundeckApplication · Jenkins

CVE-2022-41234

HIGH · 8.8 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to after 3.6.11 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Jenkins Rundeck Plugin 3.6.11 and earlier does not protect access to the /plugin/rundeck/webhook/ endpoint, allowing users with Overall/Read permission to trigger jobs that are configured to be triggerable via Rundeck.

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 confidence

The Jenkins Rundeck Plugin versions 3.6.11 and earlier lacks proper authorization checks on the /plugin/rundeck/webhook/ endpoint, allowing any user with Overall/Read permission (the minimum Jenkins permission level) to trigger Rundeck jobs that are configured to be triggerable via Rundeck webhooks.

MitigationUpgrade the Rundeck Plugin to version 3.6.12 or later, which includes proper permission checks on the webhook endpoint. Alternatively, restrict access to the webhook endpoint via network-level controls or temporarily disable Rundeck webhook triggers until the upgrade is applied.

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
Affected:<= 3.6.11

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Rundeck Plugin version
    Log into Jenkins as an administrator, navigate to Manage Jenkins > Manage Plugins > Installed tab, and locate the Rundeck plugin to read its version. Alternatively, check the plugin file directly: locate $JENKINS_HOME/plugins/rundeck.jpi or rundeck.hpi and examine its manifest or version file.
    Affected if The installed version is 3.6.11 or earlier.
  2. Confirm webhook endpoint exists
    Make an HTTP GET or POST request to the /plugin/rundeck/webhook/ endpoint on your Jenkins server. This endpoint should respond (even if with an error) if the Rundeck plugin is installed.
    Affected if The endpoint responds (the plugin is installed and the webhook feature is present).
  3. Check for Rundeck webhook-triggered jobs
    Review your Jenkins jobs that use Rundeck integration. Inspect each job's configuration and look for settings related to Rundeck webhooks, such as 'Trigger on Rundeck webhook' or webhook URL configurations in the Rundeck plugin section of the job.
    Affected if Any job is configured to be triggerable via Rundeck webhooks (the webhook trigger option is enabled in the job configuration).
  4. Verify permissions on the webhook endpoint
    Create a test Jenkins user with only Overall/Read permission (the lowest permission level). Log in as this user and attempt to access or send a request to /plugin/rundeck/webhook/ to see if the request is processed without authorization failure.
    Affected if A user with only Overall/Read permission can successfully trigger or access the webhook endpoint without being denied.

You are affected if the Rundeck plugin version is 3.6.11 or earlier AND you have jobs configured with Rundeck webhook triggers AND any user with basic read access can trigger those webhooks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 3.6.11
Interim mitigation

Upgrade the Rundeck Plugin to version 3.6.12 or later, which includes proper permission checks on the webhook endpoint. Alternatively, restrict access to the webhook endpoint via network-level controls or temporarily disable Rundeck webhook triggers until the upgrade is applied.

Recommended fix Moderate confidence

Rundeck Plugin version 3.6.12 or later

  1. Navigate to Jenkins Manage Plugins page
  2. Locate the Rundeck Plugin in the Installed tab
  3. Check the current version of the Rundeck Plugin
  4. Upgrade to the latest available version of the Rundeck Plugin that includes the security fix
  5. Restart Jenkins if required after plugin upgrade
  6. Verify that users now require appropriate permissions to trigger Rundeck jobs via the webhook endpoint

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rundeck Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41234 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41234 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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