File-parameter disclosure and tampering via permissive temporary files
Published Mar 8, 2023 · Updated Feb 28, 2025
Incorrect temporary-file permissions in Jenkins 2.393 and earlier and LTS 2.375.3 and earlier allow local users to read or alter CLI uploads. The controller writes standard-input file parameters into its default temporary directory using the process's default creation permissions. Exploitation requires controller filesystem access, a CLI-triggered build with a file parameter, and an operating system with a shared temporary directory.
Summary
What happened
Incorrect temporary-file permissions in Jenkins 2.393 and earlier and LTS 2.375.3 and earlier allow local users to read or alter CLI uploads. The controller writes standard-input file parameters into its default temporary directory using the process's default creation permissions. Exploitation requires controller filesystem access, a CLI-triggered build with a file parameter, and an operating system with a shared temporary directory.
The record
- CVE
- CVE-2023-27903
- Published
- Mar 8, 2023
- Updated
- Feb 28, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-863, T1005, T1565.001
- 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?
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