Jira Pipeline StepsApplication · Jenkins
CVE-2023-24439
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 stores the private keys unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
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 store SSH private keys used for JIRA authentication unencrypted in plaintext within the plugin's global configuration XML file on the Jenkins controller. Any user with file system access to the Jenkins controller can read these private keys.
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 tab and search for 'JIRA Pipeline Steps', or check $JENKINS_HOME/plugins for the jira-plugin folderAffected if The plugin is not listed in installed plugins, then this CVE does not apply
-
Check plugin versionIn the Installed Plugins tab, locate the JIRA Pipeline Steps plugin and note the Version column, or read the manifest file at $JENKINS_HOME/plugins/jira-plugin/META-INF/MANIFEST.MFAffected if Version is 2.0.165.v8846cf59f3db or earlier, indicating the vulnerable version is installed
-
Locate the plugin global configuration fileNavigate to $JENKINS_HOME/org.jenkinsci.plugins.jira-pipeline-steps.xml or search for XML files containing 'jira-pipeline-steps' in the $JENKINS_HOME directoryAffected if The configuration file exists on the filesystem
-
Inspect for unencrypted SSH private keysOpen the XML configuration file in a text editor and search for '<privateKey>' or similar credential elements; examine whether the private key content appears in plaintext rather than encrypted formAffected if Plaintext SSH private key material is visible in the XML file content, indicating the vulnerability is present and exploitable
A user is affected if the JIRA Pipeline Steps Plugin version is 2.0.165.v8846cf59f3db or earlier AND SSH private keys are stored in plaintext within the plugin's global XML configuration file.
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.
From vendor dataUpgrade the JIRA Pipeline Steps Plugin to version 2.0.166.vd24a3f2787a6 or later which encrypts stored credentials. Also rotate any private keys that may have been exposed.
Fix this in Jira Pipeline Steps
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24439 — 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-24439 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