Local memory leak via crafted PDF parsing
Published Aug 25, 2021 · Updated Aug 4, 2024
PoDoFo 0.9.6 contains a disputed memory leak that local users trigger by opening a crafted PDF with podofopdfinfo. The report attributes retained PdfParser allocations to PdfMemDocument::Load after IsNextToken processes the malformed file. Processing requires user interaction; the project later could not reproduce the leak, questioned the proposed cause, and closed the ticket without a test case.
Summary
What happened
PoDoFo 0.9.6 contains a disputed memory leak that local users trigger by opening a crafted PDF with podofopdfinfo. The report attributes retained PdfParser allocations to PdfMemDocument::Load after IsNextToken processes the malformed file. Processing requires user interaction; the project later could not reproduce the leak, questioned the proposed cause, and closed the ticket without a test case.
The record
- CVE
- CVE-2020-18972
- Published
- Aug 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 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
- mem-leak proof-of-concept PDFproof of concept · unverified
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