Pipeline\Application · Jenkins
CVE-2022-28156
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: Phoenix AutoTest Plugin 1.3 and earlier allows attackers with Item/Configure permission to copy arbitrary files and directories from the Jenkins controller to the agent workspace.
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: Phoenix AutoTest Plugin versions 1.3 and earlier contains a path traversal vulnerability allowing authenticated attackers with Item/Configure permission to copy arbitrary files and directories from the Jenkins controller file system to agent workspace directories. This enables unauthorized disclosure of sensitive controller files.
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\Application
<= 1.3CVSS 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 Phoenix AutoTest Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the file system at $JENKINS_HOME/plugins/ for a directory named phoenix-autotest or similar, indicating the plugin is present.Affected if The plugin directory exists in the plugins folder or the plugin appears in the Installed tab of the Jenkins plugin manager.
-
Determine the installed plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and locate the Pipeline: Phoenix AutoTest Plugin entry to read the Version column. Alternatively, check the version file within the plugin's directory at $JENKINS_HOME/plugins/phoenix-autotest/META-INF/MANIFEST.MF.Affected if The version listed is 1.3 or any version number lower than 1.4.
-
Identify users with Item/Configure permissionNavigate to Manage Jenkins > Manage Users, or review the Jenkins authorization matrix at Manage Jenkins > Configure Global Security > Authorization. Look for users or groups granted the Item/Configure permission.Affected if Any untrusted or unauthorized users have been granted Item/Configure permission, enabling them to exploit the path traversal flaw.
-
Verify if the plugin is actively used in any Pipeline jobsSearch job configurations for usages of the phoenix-autotest plugin step, or review any Pipeline scripts that reference this plugin's functionality within the job definitions.Affected if The plugin is actively used in existing Pipeline job configurations, making the path traversal vulnerability accessible through those job execution contexts.
A user is affected if the Pipeline: Phoenix AutoTest Plugin is installed at version 1.3 or earlier and untrusted users possess Item/Configure permission.
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 the Phoenix AutoTest Plugin to version 1.4 or later which addresses this vulnerability. Additionally, restrict Item/Configure permission to only trusted users and review which users have elevated permissions in the Jenkins security configuration.
Pipeline: Phoenix AutoTest Plugin version 1.4
- Navigate to Manage Jenkins > Manage Plugins
- Select the 'Installed' tab and search for 'Pipeline: Phoenix AutoTest'
- If the plugin is installed, update it to version 1.4 or later
- If the plugin is not actively used, consider removing it entirely to reduce attack surface
- After updating, verify the plugin version in the Installed tab to confirm the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28156 — 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-28156 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