Code execution via malicious file out-of-bounds write
Published Dec 10, 2024 · Updated Dec 16, 2024
Out-of-bounds write in Adobe PDFL SDK 21.0.0.5 and earlier allows context-dependent attackers to execute code via a malicious file. Adobe identifies no affected parser, function, or malformed file structure, leaving the precise unchecked write operation undisclosed. Execution requires a user to open the file, after which attacker-controlled code runs with the current user's privileges.
Summary
What happened
Out-of-bounds write in Adobe PDFL SDK 21.0.0.5 and earlier allows context-dependent attackers to execute code via a malicious file. Adobe identifies no affected parser, function, or malformed file structure, leaving the precise unchecked write operation undisclosed. Execution requires a user to open the file, after which attacker-controlled code runs with the current user's privileges.
The record
- CVE
- CVE-2024-49513
- Published
- Dec 10, 2024
- Updated
- Dec 16, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 2024CVE publishedPublication date reported by the CVE source.
- Dec 16, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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