Code execution via trusted record length
Published Feb 4, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in SoftMaker PlanMaker 2021 Revision 1014 allows attackers to execute code via a crafted Excel document. CEscherObject::ReadNativeProperties trusts a 32-bit OfficeArt record length and copies stream data into a 64-byte object member. The user must open the document; the demonstrated consequence is heap corruption and a process abort, with code execution under the application's context.
Summary
What happened
Heap-based buffer overflow in SoftMaker PlanMaker 2021 Revision 1014 allows attackers to execute code via a crafted Excel document. CEscherObject::ReadNativeProperties trusts a 32-bit OfficeArt record length and copies stream data into a 64-byte object member. The user must open the document; the demonstrated consequence is heap corruption and a process abort, with code execution under the application's context.
The record
- CVE
- CVE-2020-27248
- Published
- Feb 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- SoftMaker Software GmbH
- Product
- PlanMaker
- Classifications
- CWE-122, CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 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 PlanMaker 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
- Talos crafted Excel document 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