Process crash via BDCNode destructor null dereference
Published Sep 20, 2021 · Updated Aug 4, 2024
NULL pointer dereference in pdftools through 20200714 allows local users to crash the application through crafted input. The node::BDCNode destructor in bdcnode.cpp dereferences a null pointer when it handles the triggering input, terminating the process. The public record does not disclose which input value creates the null state; exploitation requires user interaction and only interrupts the process.
Summary
What happened
NULL pointer dereference in pdftools through 20200714 allows local users to crash the application through crafted input. The node::BDCNode destructor in bdcnode.cpp dereferences a null pointer when it handles the triggering input, terminating the process. The public record does not disclose which input value creates the null state; exploitation requires user interaction and only interrupts the process.
The record
- CVE
- CVE-2021-39539
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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