Arbitrary file read via symlink-following artifact collection
Published Oct 25, 2023 · Updated Feb 13, 2025
Arbitrary file read in Jenkins CloudBees CD Plugin 1.1.32 and earlier allows remote authenticated users to publish controller files. During the CloudBees CD - Publish Artifact post-build step, artifact collection follows workspace symbolic links outside the controller's temporary directory. Job-configuration permission and a previously configured CloudBees CD server are required, and exposure is limited to files readable by the Jenkins controller process.
Summary
What happened
Arbitrary file read in Jenkins CloudBees CD Plugin 1.1.32 and earlier allows remote authenticated users to publish controller files. During the CloudBees CD - Publish Artifact post-build step, artifact collection follows workspace symbolic links outside the controller's temporary directory. Job-configuration permission and a previously configured CloudBees CD server are required, and exposure is limited to files readable by the Jenkins controller process.
The record
- CVE
- CVE-2023-46655
- Published
- Oct 25, 2023
- Updated
- Feb 13, 2025
- Vendor
- Jenkins Project
- Product
- CloudBees CD Plugin
- Classifications
- CWE-59, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1.32
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo