Jira Pipeline StepsApplication · Jenkins
CVE-2023-24438
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 · uneditedA missing permission check in Jenkins JIRA Pipeline Steps Plugin 2.0.165.v8846cf59f3db and earlier allows attackers with Overall/Read permission 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 · high confidenceMissing permission check in Jenkins JIRA Pipeline Steps Plugin versions 2.0.165.v8846cf59f3db and earlier allows authenticated users with only Overall/Read permission to make arbitrary HTTP connections to attacker-specified URLs using credential IDs, potentially exfiltrating stored Jenkins 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
Jira Pipeline StepsApplication
<= 2.0.165.v8846cf59f3dbCVSS 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.
-
Verify JIRA Pipeline Steps plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or run: Jenkins.instance.pluginManager.getPlugin('jira').theObject.version via script consoleAffected if Plugin is not listed or not found in the plugin manager
-
Check installed plugin versionIn the Installed Plugins tab, locate 'JIRA Pipeline Steps' and note the Version column. Compare against 2.0.165.v8846cf59f3dbAffected if Version is 2.0.165.v8846cf59f3db or earlier
-
Identify pipelines using JIRA stepsSearch job configurations for 'jira' or 'jira:' steps (e.g., jiraIssueSelector, jiraComment, jiraSendBuildInfo), or run: Jenkins.instance.allItems.flatten().findAll{it.class.simpleName == 'WorkflowJob'}.collect{it.name} via script console and inspect their scriptsAffected if Any pipelines use JIRA plugin steps and the plugin version is affected
-
Audit user permissionsNavigate to Manage Jenkins > Manage Users, or check authorization matrix at Manage Jenkins > Configure Global Security. Identify users with Overall/Read permissionAffected if Users with only Overall/Read permission exist and the JIRA Pipeline Steps plugin is installed with an affected version
A user is affected if the JIRA Pipeline Steps plugin version is 2.0.165.v8846cf59f3db or earlier AND the plugin is installed AND pipelines use JIRA steps AND users with Overall/Read permission exist in the instance.
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 JIRA Pipeline Steps Plugin to the latest patched version once released. As a compensating control, restrict Overall/Read permission to only necessary users and audit stored credentials.
2.0.166.v0045ec982fb0 or later
- 1. Navigate to Jenkins dashboard
- 2. Go to Manage Jenkins > Manage Plugins
- 3. Select the 'Installed' tab
- 4. Find 'JIRA Pipeline Steps' plugin in the list
- 5. If an update is available, click 'Update' or upgrade to the fixed version
- 6. Restart Jenkins if required after 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
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24438 — 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-2023-24438 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