Jenkins 2.587 and earlier, LTS 2.580.1 and earlier checks for symbolic links in the path of an extracted file only before creating its paren
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Jenkins, the open-source automation server, is affected by this vulnerability. An attacker with Item/Configure permission could exploit a time-of-check/time-of-use flaw in archive extraction to write files to arbitrary locations on the Jenkins controller's file system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Jenkins 2.587 and earlier, LTS 2.580.1 and earlier checks for symbolic links in the path of an extracted file only before creating its parent directories, not immediately before writing it, and allows symbolic links in artifacts to replace existing files or empty directories, allowing attackers with Item/Configure permission to write files to arbitrary locations on the Jenkins controller file system.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Jenkins Project Jenkins
Version range not reported