Application crash via malformed SVG parsing
Published Sep 1, 2021 · Updated Sep 17, 2024
Memory corruption in Adobe Bridge 11.1 and earlier allows local users to crash the application by opening a malicious SVG file. The SVG parser accesses memory after the end of a buffer while handling crafted SVG input; Adobe does not identify the affected routine. Exploitation requires the current user to open the file and is limited to terminating the Bridge process, with no reported data disclosure or modification.
Summary
What happened
Memory corruption in Adobe Bridge 11.1 and earlier allows local users to crash the application by opening a malicious SVG file. The SVG parser accesses memory after the end of a buffer while handling crafted SVG input; Adobe does not identify the affected routine. Exploitation requires the current user to open the file and is limited to terminating the Bridge process, with no reported data disclosure or modification.
The record
- CVE
- CVE-2021-36077
- Published
- Sep 1, 2021
- Updated
- Sep 17, 2024
- Vendor
- Adobe
- Product
- Adobe Bridge
- Classifications
- CWE-788, CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=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