Code execution via out-of-bounds project-file writes
Published Jan 26, 2021 · Updated Aug 4, 2024
Out-of-bounds writes in Delta Electronics TPEditor 1.98 and earlier allow attackers to execute code by opening a crafted TPE project file. The TPE file parser fails to validate user-supplied data before writing past the end of an allocated buffer at two parsing sites. Exploitation requires a user to open the malicious file or visit a page that supplies it, and resulting code runs in the TPEditor process.
Summary
What happened
Out-of-bounds writes in Delta Electronics TPEditor 1.98 and earlier allow attackers to execute code by opening a crafted TPE project file. The TPE file parser fails to validate user-supplied data before writing past the end of an allocated buffer at two parsing sites. Exploitation requires a user to open the malicious file or visit a page that supplies it, and resulting code runs in the TPEditor process.
The record
- CVE
- CVE-2020-27284
- Published
- Jan 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Delta Electronics, Inc.
- Product
- TPEditor
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 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=v1.98 and prior
What conditions does exploitation require?
What is affected?
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
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