Code execution via out-of-bounds memory access
Published Sep 1, 2021 · Updated Apr 23, 2025
Memory corruption in Adobe Bridge 11.1 and earlier allows local users to execute arbitrary code by opening a malicious Bridge file. Adobe identifies an access-after-end-of-buffer error but has not disclosed the affected parser or the operation that crosses the buffer boundary. Exploitation requires the current user to open the crafted file, and resulting code runs with that user's privileges.
Summary
What happened
Memory corruption in Adobe Bridge 11.1 and earlier allows local users to execute arbitrary code by opening a malicious Bridge file. Adobe identifies an access-after-end-of-buffer error but has not disclosed the affected parser or the operation that crosses the buffer boundary. Exploitation requires the current user to open the crafted file, and resulting code runs with that user's privileges.
The record
- CVE
- CVE-2021-36067
- Published
- Sep 1, 2021
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- Adobe Bridge
- Classifications
- CWE-788, CWE-119, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 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 <=11.1
- 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