Code execution via EPS BoundingBox buffer overflow
Published Mar 25, 2020 · Updated Aug 4, 2024
Stack-based buffer overflow in Adobe Photoshop CC 2019 20.0.8 and earlier and Photoshop 2020 21.1 and earlier allows attackers to execute code. The EPS parser copies an unvalidated user-supplied BoundingBox element into a fixed-size stack buffer, causing a stack-based overflow. Exploitation requires opening a malicious file or visiting a malicious page and runs code in the Photoshop process under the current user's account.
Summary
What happened
Stack-based buffer overflow in Adobe Photoshop CC 2019 20.0.8 and earlier and Photoshop 2020 21.1 and earlier allows attackers to execute code. The EPS parser copies an unvalidated user-supplied BoundingBox element into a fixed-size stack buffer, causing a stack-based overflow. Exploitation requires opening a malicious file or visiting a malicious page and runs code in the Photoshop process under the current user's account.
The record
- CVE
- CVE-2020-3780
- Published
- Mar 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Adobe
- Product
- Adobe Photoshop
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=Photoshop CC 2019, and Photoshop 2020 versions
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