Application crash via null pointer dereference
Published Dec 10, 2024 · Updated Jan 16, 2025
NULL pointer dereference in affected Adobe Acrobat Reader releases allows attackers to crash the application via a crafted file. Adobe has not disclosed the affected component or the specific operation that dereferences the null pointer. Opening the crafted file is required, and successful exploitation terminates the Reader process without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in affected Adobe Acrobat Reader releases allows attackers to crash the application via a crafted file. Adobe has not disclosed the affected component or the specific operation that dereferences the null pointer. Opening the crafted file is required, and successful exploitation terminates the Reader process without reported data disclosure or modification.
The record
- CVE
- CVE-2024-49531
- Published
- Dec 10, 2024
- Updated
- Jan 16, 2025
- Vendor
- Adobe
- Product
- Adobe Acrobat Reader
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 2024CVE publishedPublication date reported by the CVE source.
- Jan 16, 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=0 <=20.005.30710
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.
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