dbcve.org
Cloudbees CdApplication · Jenkins

CVE-2023-46655

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 1.1.32 or later.
See remediation →
71/100
Remediation priority · Elevated
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 directory from which artifacts are published during the 'CloudBees CD - Publish Artifact' post-build step, allowing attackers able to configure jobs to publish arbitrary files from the Jenkins controller file system to the previously configured CloudBees CD server.

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 confidence

The CloudBees CD Plugin for Jenkins versions 1.1.32 and earlier fails to validate symbolic links during artifact publishing. When using the 'CloudBees CD - Publish Artifact' post-build step, the plugin follows symlinks that point outside the intended artifact directory, allowing authenticated attackers with job configuration permissions to read and exfiltrate arbitrary files from the Jenkins controller filesystem to a configured CloudBees CD server.

MitigationUpgrade the CloudBees CD Plugin to a version newer than 1.1.32 when available, and limit job configuration permissions to trusted users only until the patch can be applied.

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
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 checks

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

  1. Verify CloudBees CD plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and locate the 'CloudBees CD' or 'Cloudbees Cd' plugin to determine its installed version
    Affected if The installed version is 1.1.32 or earlier
  2. Identify jobs using CloudBees CD Publish Artifact
    Search job configurations for the 'CloudBees CD - Publish Artifact' post-build step: go to each job > Configure and look for this post-build action, or use Jenkins script console to search: Jenkins.instance.allItems.each { job -> if (job.hasProperty('builds') && job.lastBuild?.actions.find { it.toString().contains('Publish Artifact') }) { println job.fullName } }
    Affected if Any job is configured with the 'CloudBees CD - Publish Artifact' post-build action
  3. Audit job configuration permissions
    Review which users or groups have Job/Configure permission: go to Manage Jenkins > Manage and Assign Roles > Manage Roles, or review project-based matrix authorization settings
    Affected if Users who are not fully trusted have Job/Configure permissions on jobs that use the CloudBees CD Publish Artifact step

The environment is affected if the CloudBees CD plugin version is 1.1.32 or earlier AND at least one job uses the 'CloudBees CD - Publish Artifact' post-build step with potentially untrusted users having job configuration permissions.

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 the CloudBees CD Plugin to a version newer than 1.1.32 when available, and limit job configuration permissions to trusted users only until the patch can be applied.

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 'Updates' tab
  4. Find 'CloudBees CD' plugin in the list
  5. Check if version 1.1.33 or later is available in the updates
  6. If available, select the plugin and click 'Download now and install after restart'
  7. Wait for the plugin to update and Jenkins to restart
  8. Alternatively, download the .hpi file for version 1.1.33 or later from the Jenkins plugin repository and upload it via 'Advanced' settings in Manage Plugins

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

Fix this in Cloudbees Cd Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46655 — 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-46655 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