dbcve.org
Cloudbees CdApplication · Jenkins

CVE-2023-46654

HIGH · 8.1 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 1.1.32 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Jenkins CloudBees CD Plugin 1.1.32 and earlier follows symbolic links to locations outside of the expected directory during the cleanup process of the 'CloudBees CD - Publish Artifact' post-build step, allowing attackers able to configure jobs to delete arbitrary files on 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 · moderate confidence

The CloudBees CD Plugin for Jenkins versions 1.1.32 and earlier fails to validate that symbolic links remain within the expected workspace directory during the cleanup process of the 'CloudBees CD - Publish Artifact' post-build step. Attackers with job configuration permissions can create symlinks pointing outside the workspace, causing the plugin to delete arbitrary files on the Jenkins controller file system.

MitigationUpgrade CloudBees CD Plugin to version 1.2 or later to obtain the fix. Additionally, restrict job configuration permissions to trusted users and audit existing jobs for any maliciously placed symlinks.

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
Cloudbees CdApplication
Affected:<= 1.1.32

CVSS 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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check CloudBees CD Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and locate 'CloudBees CD' or 'CloudBees Flow' in the list. The version is displayed in the Version column.
    Affected if The installed version is 1.1.32 or earlier.
  2. Identify jobs using the vulnerable post-build step
    Navigate to each job configuration and inspect the 'Post-build Actions' section. Look for 'CloudBees CD - Publish Artifact' or similar CloudBees CD post-build steps. Alternatively, search Jenkins configuration XML files for 'cloudbees-cd' or 'CloudBeesCD' post-build elements.
    Affected if Any job is configured with the 'CloudBees CD - Publish Artifact' post-build action.
  3. Inspect workspace directories for external symlinks
    On the Jenkins controller, navigate to each job's workspace directory (typically in $JENKINS_HOME/workspace/). Run 'ls -la' and check for symbolic links pointing outside the workspace (use 'readlink -f <symlink>' to resolve the full path).
    Affected if Any symlink in a workspace directory resolves to a path outside that workspace.

A user is affected if the CloudBees CD Plugin version is 1.1.32 or earlier AND any job uses the 'CloudBees CD - Publish Artifact' post-build step, or if external symlinks exist in workspaces.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.1.32
Interim mitigation

Upgrade CloudBees CD Plugin to version 1.2 or later to obtain the fix. Additionally, restrict job configuration permissions to trusted users and audit existing jobs for any maliciously placed symlinks.

Recommended fix Moderate confidence

CloudBees CD plugin version 1.1.33 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the 'CloudBees CD' plugin in the list
  5. If a newer version is available, select it and click 'Download now and install after restart'
  6. Wait for the plugin to update and Jenkins to restart
  7. Verify the new version is >= 1.1.33 in the installed plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloudbees Cd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46654 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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