Heap corruption via record-length integer overflow
Published Feb 10, 2021 · Updated Aug 4, 2024
Integer overflow in TextMaker 2021 revision 1014 allows context-dependent attackers to corrupt heap memory via a crafted document. The record 0x002a parser reads a 32-bit length from the document, miscalculates the required heap allocation, and later writes beyond that buffer. Exploitation requires a victim to open the document, after which the out-of-bounds write corrupts application heap memory.
Summary
What happened
Integer overflow in TextMaker 2021 revision 1014 allows context-dependent attackers to corrupt heap memory via a crafted document. The record 0x002a parser reads a 32-bit length from the document, miscalculates the required heap allocation, and later writes beyond that buffer. Exploitation requires a victim to open the document, after which the out-of-bounds write corrupts application heap memory.
The record
- CVE
- CVE-2020-13546
- Published
- Feb 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- SoftMaker Software GmbH
- Product
- TextMaker
- Classifications
- CWE-787, CWE-131, CWE-190, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=SoftMaker Software GmbH SoftMaker Office TextMaker 2021 (revision 1014)
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Cisco Talos record 0x002a proof of conceptproof 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