User-context code execution via use-after-free
Published Jun 26, 2020 · Updated May 5, 2025
Use-after-free in Adobe Bridge 10.0.1 and earlier allows attackers to execute arbitrary code after required user interaction. Adobe has not published the affected component or the stale-object operation that causes the freed memory to be reused. Successful exploitation runs code in the context of the current user, bounding access to that user's privileges.
Summary
What happened
Use-after-free in Adobe Bridge 10.0.1 and earlier allows attackers to execute arbitrary code after required user interaction. Adobe has not published the affected component or the stale-object operation that causes the freed memory to be reused. Successful exploitation runs code in the context of the current user, bounding access to that user's privileges.
The record
- CVE
- CVE-2020-9566
- Published
- Jun 26, 2020
- Updated
- May 5, 2025
- Vendor
- Adobe
- Product
- Adobe Bridge
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2020CVE publishedPublication date reported by the CVE source.
- May 5, 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=10.0.1 and earlier version versions
What conditions does exploitation require?
What is affected?
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.
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