Arbitrary file overwrite via insecure temporary directory
Published Sep 27, 2021 · Updated Sep 17, 2024
Arbitrary file write in Adobe Creative Cloud Desktop 5.4 and earlier allows local users to overwrite files through insecure temporary-file handling. The application creates a temporary file in a directory whose permissions permit unsafe file replacement, but Adobe has not identified the affected routine. Exploitation is limited to macOS and requires local access, administrator privileges, and user interaction; the bounded impact is arbitrary file-system write.
Summary
What happened
Arbitrary file write in Adobe Creative Cloud Desktop 5.4 and earlier allows local users to overwrite files through insecure temporary-file handling. The application creates a temporary file in a directory whose permissions permit unsafe file replacement, but Adobe has not identified the affected routine. Exploitation is limited to macOS and requires local access, administrator privileges, and user interaction; the bounded impact is arbitrary file-system write.
The record
- CVE
- CVE-2021-28613
- Published
- Sep 27, 2021
- Updated
- Sep 17, 2024
- Vendor
- Adobe
- Product
- Adobe Creative Cloud Desktop
- Classifications
- CWE-379, T1565.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 27, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record 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=unspecified <=5.4
- Affected versionversion=unspecified <=None
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