Code execution via excess STL vertices
Published Feb 24, 2021 · Updated Aug 4, 2024
Stack-based buffer overflow in OpenSCAD 2020.12-RC2 allows context-dependent attackers to execute code via a crafted ASCII STL file. The import_stl() parser accepts more than three vertex lines in one outer loop and uses the unchecked index to write beyond its fixed vdata[3][3] stack array. A victim must import the attacker-supplied file; successful exploitation runs code with the application's privileges, while failed attempts can crash it.
Summary
What happened
Stack-based buffer overflow in OpenSCAD 2020.12-RC2 allows context-dependent attackers to execute code via a crafted ASCII STL file. The import_stl() parser accepts more than three vertex lines in one outer loop and uses the unchecked index to write beyond its fixed vdata[3][3] stack array. A victim must import the attacker-supplied file; successful exploitation runs code with the application's privileges, while failed attempts can crash it.
The record
- CVE
- CVE-2020-28599
- Published
- Feb 24, 2021
- Updated
- Aug 4, 2024
- Vendor
- OpenSCAD
- Product
- OpenSCAD
- Classifications
- CWE-121, CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 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=Openscad openscad-2020.12-RC2
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 crafted ASCII STL 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