Code execution via SVG heap buffer overflow
Published Aug 11, 2022 · Updated Apr 23, 2025
Heap-based buffer overflow in Adobe FrameMaker 2019 Update 8 and earlier and 2020 Update 4 and earlier allows attackers to execute code via an SVG file. Public disclosures identify the SVG parser and a heap overwrite but do not identify the affected field or the operation that exceeds the allocation. Exploitation requires a victim to open a malicious file, and successful code runs with the victim's current-user privileges.
Summary
What happened
Heap-based buffer overflow in Adobe FrameMaker 2019 Update 8 and earlier and 2020 Update 4 and earlier allows attackers to execute code via an SVG file. Public disclosures identify the SVG parser and a heap overwrite but do not identify the affected field or the operation that exceeds the allocation. Exploitation requires a victim to open a malicious file, and successful code runs with the victim's current-user privileges.
The record
- CVE
- CVE-2022-35676
- Published
- Aug 11, 2022
- Updated
- Apr 23, 2025
- Vendor
- Adobe
- Product
- Adobe FrameMaker
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2022CVE 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 <=2019u8
- Affected versionversion=unspecified <=2020u4
- 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