Process-data disclosure and crash via crafted PDF
Published Mar 8, 2020 · Updated Aug 4, 2024
Heap corruption in npdf.dll in Nitro Pro before 13.13.2.242 allows remote attackers to corrupt memory via a crafted PDF document. The public record identifies nitro::get_property+2381 as the faulting location but does not disclose the malformed property or erroneous memory operation. Opening the file is required, and successful triggering can expose process data or interrupt the application without modifying data.
Summary
What happened
Heap corruption in npdf.dll in Nitro Pro before 13.13.2.242 allows remote attackers to corrupt memory via a crafted PDF document. The public record identifies nitro::get_property+2381 as the faulting location but does not disclose the malformed property or erroneous memory operation. Opening the file is required, and successful triggering can expose process data or interrupt the application without modifying data.
The record
- CVE
- CVE-2020-10222
- Published
- Mar 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 8, 2020CVE 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
- Nafiez heap-corruption demonstrationproof 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