Code execution via arbitrary file overwrite
Published Mar 12, 2021 · Updated Apr 23, 2025
File handling in Adobe Creative Cloud Desktop 5.3 and earlier allows physically proximate attackers to overwrite arbitrary files. Adobe has not published the affected file-handling locus or how it selects or opens an attacker-influenced overwrite destination. Exploitation requires physical access, high privileges, and user interaction, and Adobe states that the overwrite can lead to code execution in the current user's context.
Summary
What happened
File handling in Adobe Creative Cloud Desktop 5.3 and earlier allows physically proximate attackers to overwrite arbitrary files. Adobe has not published the affected file-handling locus or how it selects or opens an attacker-influenced overwrite destination. Exploitation requires physical access, high privileges, and user interaction, and Adobe states that the overwrite can lead to code execution in the current user's context.
The record
- CVE
- CVE-2021-21068
- Published
- Mar 12, 2021
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- Adobe Creative Cloud Desktop
- Classifications
- CWE-379
- Attack vector
- physical
- Privileges
- admin
Timeline
How it unfolded
- Mar 12, 2021CVE publishedPublication date reported by the CVE source.
- Apr 23, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=5.3
- 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