File overwrite via predictable temporary paths
Published May 30, 2023 · Updated Jan 10, 2025
Link-following in imapsync 2.229 and earlier allows local users to overwrite files owned by the account that runs imapsync. With default options, the PID-file path /tmp/imapsync.pid is predictable, and ordinary file writes follow an attacker-created symbolic link. Exploitation requires write access to the shared temporary directory and a victim account to run imapsync; the overwrite carries that account's file privileges.
Summary
What happened
Link-following in imapsync 2.229 and earlier allows local users to overwrite files owned by the account that runs imapsync. With default options, the PID-file path /tmp/imapsync.pid is predictable, and ordinary file writes follow an attacker-created symbolic link. Exploitation requires write access to the shared temporary directory and a victim account to run imapsync; the overwrite carries that account's file privileges.
The record
- CVE
- CVE-2023-34204
- Published
- May 30, 2023
- Updated
- Jan 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-59, T1565.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 30, 2023CVE publishedPublication date reported by the CVE source.
- Jan 10, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Secure /tmp usage symbolic-link proof of conceptproof of concept · demonstrated
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