Code execution via malformed STL vertex parsing
Published May 10, 2021 · Updated Aug 4, 2024
Out-of-bounds write in OpenSCAD 2020.12-RC2 allows attackers to execute code when a crafted ASCII STL file is imported. In import_stl(), a failed vertex-number conversion sets the row index to 10, after which the next vertex writes attacker-controlled values beyond the three-row vdata stack array. Exploitation requires a user to import the malicious file; the overwrite can corrupt a shared-pointer control value and redirect execution during destruction.
Summary
What happened
Out-of-bounds write in OpenSCAD 2020.12-RC2 allows attackers to execute code when a crafted ASCII STL file is imported. In import_stl(), a failed vertex-number conversion sets the row index to 10, after which the next vertex writes attacker-controlled values beyond the three-row vdata stack array. Exploitation requires a user to import the malicious file; the overwrite can corrupt a shared-pointer control value and redirect execution during destruction.
The record
- CVE
- CVE-2020-28600
- Published
- May 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- OpenSCAD
- Product
- OpenSCAD
- Classifications
- CWE-119, CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 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=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
- TALOS-2020-1224 malformed 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