dbcve.org
Jira Pipeline StepsApplication · Jenkins

CVE-2023-24437

HIGH · 8.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to after 2.0.165.v8846cf59f3db or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A cross-site request forgery (CSRF) vulnerability in Jenkins JIRA Pipeline Steps Plugin 2.0.165.v8846cf59f3db and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing 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 · moderate confidence

CSRF vulnerability in Jenkins JIRA Pipeline Steps Plugin versions 2.0.165.v8846cf59f3db and earlier allows authenticated attackers to trigger the plugin to connect to attacker-specified URLs using attacker-specified credential IDs, potentially exfiltrating stored Jenkins credentials.

MitigationUpgrade JIRA Pipeline Steps Plugin to version 2.0.166.vcbf8a_6f2d9d4 or later. If immediate upgrade is not possible, consider disabling the plugin or restricting plugin access via Matrix-based security.

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
Jira Pipeline StepsApplication
Affected:<= 2.0.165.v8846cf59f3db

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify JIRA Pipeline Steps plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'JIRA Pipeline Steps' or check the plugin directory $JENKINS_HOME/plugins for a folder named 'jira' or 'jira-pipeline-steps'
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In Manage Jenkins > Manage Plugins > Installed, find JIRA Pipeline Steps and note the version column. Alternatively, inspect $JENKINS_HOME/plugins/jira/META-INF/MANIFEST.MF for the Implementation-Version
    Affected if Version is 2.0.165.v8846cf59f3db or earlier
  3. Confirm Jenkins authentication is enabled
    Navigate to Manage Jenkins > Configure Global Security and verify that 'Jenkins' own user database' or an external authentication realm is selected under Security Realm
    Affected if Authentication is enabled (this is the default and required for the attack to leverage stolen credentials)
  4. Check for stored credentials usable by the plugin
    Navigate to Manage Jenkins > Manage Credentials and review any credentials (username/password, API tokens, etc.) scoped to Jenkins that could be used for JIRA authentication
    Affected if Any credentials exist in Jenkins that the plugin could potentially use

You are affected if JIRA Pipeline Steps plugin version 2.0.165.v8846cf59f3db or earlier is installed and Jenkins authentication is enabled, regardless of whether credentials are currently configured for JIRA.

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 2.0.165.v8846cf59f3db
Interim mitigation

Upgrade JIRA Pipeline Steps Plugin to version 2.0.166.vcbf8a_6f2d9d4 or later. If immediate upgrade is not possible, consider disabling the plugin or restricting plugin access via Matrix-based security.

Recommended fix Moderate confidence

JIRA Pipeline Steps plugin version 2.0.166 or later (check Jenkins plugin repository for exact fixed version)

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Search for 'JIRA Pipeline Steps' in the plugin list
  5. 5. If an update is available, select the plugin and click 'Download now and install after restart'
  6. 6. Alternatively, manually download the fixed version from the Jenkins plugin repository
  7. 7. Restart Jenkins to complete the update

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

Fix this in Jira Pipeline Steps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24437 — 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-2023-24437 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