Current-user code execution via incompatible-type resource access
Published Sep 13, 2024 · Updated Sep 13, 2024
Type confusion in Adobe Acrobat and Reader allows attackers to execute code as the current user when a malicious file is opened. A resource is accessed through a type incompatible with its actual object type, causing a logic error; Adobe has not identified the resource or parser locus. Exploitation requires a victim to open the file and yields code execution with that user's privileges.
Summary
What happened
Type confusion in Adobe Acrobat and Reader allows attackers to execute code as the current user when a malicious file is opened. A resource is accessed through a type incompatible with its actual object type, causing a logic error; Adobe has not identified the resource or parser locus. Exploitation requires a victim to open the file and yields code execution with that user's privileges.
The record
- CVE
- CVE-2024-45112
- Published
- Sep 13, 2024
- Updated
- Sep 13, 2024
- Vendor
- Adobe
- Product
- Adobe Acrobat
- Classifications
- CWE-843, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 13, 2024CVE publishedPublication date reported by the CVE source.
- Sep 13, 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=0 <=24.002.21005
- Affected versionversion=0 <=24.003.20054
- Affected versionversion=20.0 <=20.005.30655
- Affected versionversion=24.0 <=24.001.30159
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