Jira Pipeline StepsApplication · Jenkins
CVE-2023-24440
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 JIRA Pipeline Steps Plugin 2.0.165.v8846cf59f3db and earlier transmits the private key in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure.
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 JIRA Pipeline Steps Plugin versions 2.0.165.v8846cf59f3db and earlier transmits private keys in plain text as part of the global Jenkins configuration form submission, potentially exposing them during transmission or in server logs.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 and search for 'Jira Pipeline Steps' in the list of installed plugins.Affected if Plugin is not installed means not affected
-
Check installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, locate Jira Pipeline Steps and note the Version column. Compare against 2.0.165.v8846cf59f3db.Affected if Version is 2.0.165.v8846cf59f3db or earlier
-
Inspect plugin configuration for private keysGo to Manage Jenkins > Configure System > look for the 'Jira Pipeline Steps' or 'Jira' configuration section. Check if any private key fields contain configured values.Affected if Private key fields contain configured values and plugin version is vulnerable
User is affected only if Jira Pipeline Steps plugin version is 2.0.165.v8846cf59f3db or earlier AND private keys are configured in the plugin settings.
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 to version 2.0.166.vc6b_5b_8c2d14 or later which addresses this vulnerability by securing the private key transmission in the configuration form.
Version 2.0.166 or later (upgrade to latest available version)
- Navigate to Manage Jenkins > Manage Plugins
- Select the 'Installed' tab
- Locate the 'JIRA Pipeline Steps' plugin in the list
- If an update is available, select the plugin and click 'Update'
- Alternatively, download the fixed version from the Jenkins plugin repository
- Restart Jenkins if required to apply 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
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24440 — 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-24440 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