Memory corruption via multi-code-point txtwrite mapping
Published Feb 4, 2024 · Updated May 22, 2025
Memory corruption in Artifex Ghostscript before 9.53.0 allows context-dependent attackers to crash its process via a crafted PDF. The txtwrite device in devices/vector/gdevtxtw.c mishandles a character whose mapping expands to multiple Unicode code points, causing an out-of-bounds write and use-after-free. The crafted PDF must be processed with txtwrite; the bounded documented consequence is Ghostscript process memory corruption and termination.
Summary
What happened
Memory corruption in Artifex Ghostscript before 9.53.0 allows context-dependent attackers to crash its process via a crafted PDF. The txtwrite device in devices/vector/gdevtxtw.c mishandles a character whose mapping expands to multiple Unicode code points, causing an out-of-bounds write and use-after-free. The crafted PDF must be processed with txtwrite; the bounded documented consequence is Ghostscript process memory corruption and termination.
The record
- CVE
- CVE-2020-36773
- Published
- Feb 4, 2024
- Updated
- May 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2024CVE publishedPublication date reported by the CVE source.
- May 22, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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