Service crash via null pointer dereference
Published Nov 10, 2021 · Updated Aug 4, 2024
NULL pointer dereference in ObjectStream::getObject in pdf2json 0.71 allows remote attackers to crash the converter with a crafted PDF. While parsing the malformed file, ObjectStream::getObject dereferences address zero in XRef.cc instead of rejecting the invalid object stream. Processing requires no privileges or user interaction and terminates the process, limiting the demonstrated impact to a service interruption.
Summary
What happened
NULL pointer dereference in ObjectStream::getObject in pdf2json 0.71 allows remote attackers to crash the converter with a crafted PDF. While parsing the malformed file, ObjectStream::getObject dereferences address zero in XRef.cc instead of rejecting the invalid object stream. Processing requires no privileges or user interaction and terminates the process, limiting the demonstrated impact to a service interruption.
The record
- CVE
- CVE-2020-23879
- Published
- Nov 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 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.
Weakness, pattern, technique
Public exploit references
- 00-NULL-pointer-dereference-ObjectStream-getObject.pdfproof of concept · demonstrated
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