Insecure Deserialization of .cleanshot Files in CleanShot X
- 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
- Fix
- Fixed in 4.5.2, 4.6.3, 4.7.8, 4.8.10
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
CleanShot X, a screenshot and annotation app for macOS, is affected when it opens a malicious .cleanshot project file. Successful exploitation could allow an attacker to run arbitrary code with the privileges of the current user.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
CleanShot X for macOS insecurely deserializes untrusted data embedded in a .cleanshot project file (editable screenshot annotations). Exploitation requires an attacker to craft a malicious .cleanshot file, deliver it to the target, and have the target open it; the payload then executes automatically during parsing, resulting in arbitrary code execution in the context of the current user. Users who have never opened a .cleanshot file from an untrusted source are not affected by this vulnerability. This vulnerability was fixed in versions: 4.5.2, 4.6.3, 4.7.8 and 4.8.10
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- MTW CleanShot X
From 4.0.0 · fixed in 4.5.2; From 4.6.0 · fixed in 4.6.3; From 4.7.0 · fixed in 4.7.8; From 4.8.0 · fixed in 4.8.10