Pipeline Utility StepsApplication · Jenkins
CVE-2022-45381
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 Pipeline Utility Steps Plugin 2.13.1 and earlier does not restrict the set of enabled prefix interpolators and bundles versions of Apache Commons Configuration library that enable the 'file:' prefix interpolator by default, allowing attackers able to configure Pipelines to read arbitrary files from 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 Pipeline Utility Steps Plugin 2.13.1 and earlier fails to restrict enabled prefix interpolators in Apache Commons Configuration, enabling the 'file:' prefix by default. Attackers with Pipeline configuration permissions can exploit this to read arbitrary files from the Jenkins controller filesystem.
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
Pipeline Utility StepsApplication
< 2.13.2CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Check Pipeline Utility Steps plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab. Search for 'Pipeline Utility Steps' and note the version number shown.Affected if Version is 2.13.1 or earlier (versions below 2.13.2)
-
Verify plugin is actively usedSearch your Jenkins jobs for Pipeline jobs that use steps from the Pipeline Utility Steps plugin, such as configFile, readProperties, readYaml, readJSON, or other utility steps.Affected if The plugin is installed AND any Pipeline jobs reference its steps (the plugin need not be in use for the vulnerability to exist, but active use increases exposure)
-
Check for custom interpolator configurationLook in Jenkins system configuration (Manage Jenkins > Configure System) for any Apache Commons Configuration settings or custom prefix interpolator configurations related to the Pipeline Utility Steps plugin.Affected if No custom restrictions are configured for the 'file:' prefix interpolator, meaning it remains enabled by default
-
Review Pipeline permissionsUnder Manage Jenkins > Manage Users, identify which users have Pipeline configuration permissions (ability to create/edit Pipeline jobs).Affected if Users other than administrators have Pipeline configuration permissions, allowing them to craft malicious Pipeline scripts
Your environment is affected if the Pipeline Utility Steps plugin is version 2.13.1 or earlier AND users with Pipeline configuration permissions exist, since the default 'file:' prefix interpolator in Apache Commons Configuration allows arbitrary file reads.
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 · scoped2.13.2
Update the Pipeline Utility Steps Plugin to a patched version and explicitly restrict or disable the 'file:' prefix interpolator in Apache Commons Configuration settings.
2.13.2
- 1. Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
- 2. Go to the 'Installed' tab
- 3. Locate 'Pipeline Utility Steps' plugin in the list
- 4. If the installed version is below 2.13.2, click 'Update' to upgrade to version 2.13.2 or later
- 5. After update completes, restart Jenkins (or click 'Restart' if prompted)
- 6. Verify the upgrade by checking Plugin Manager > Installed > Pipeline Utility Steps shows version 2.13.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pipeline Utility Steps
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45381 — 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-2022-45381 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