Code execution via writable plugin upload temporary file
Published Mar 8, 2023 · Updated Feb 28, 2025
Insecure temporary-file permissions in Jenkins 2.393 and earlier and LTS 2.375.3 and earlier allow local users to alter uploaded plugins. Plugin uploads are staged in the shared system temporary directory with the process default creation mode instead of restrictive permissions. Exploitation requires controller filesystem access and an administrator-initiated upload; readable files expose plugin content, while writable files enable code execution.
Summary
What happened
Insecure temporary-file permissions in Jenkins 2.393 and earlier and LTS 2.375.3 and earlier allow local users to alter uploaded plugins. Plugin uploads are staged in the shared system temporary directory with the process default creation mode instead of restrictive permissions. Exploitation requires controller filesystem access and an administrator-initiated upload; readable files expose plugin content, while writable files enable code execution.
The record
- CVE
- CVE-2023-27899
- Published
- Mar 8, 2023
- Updated
- Feb 28, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-863, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 8, 2023CVE publishedPublication date reported by the CVE source.
- Feb 28, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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