Application crash via missing annotation newline bounds check
Published Aug 29, 2022 · Updated Aug 2, 2024
Out-of-bounds read in OpenSCAD's annotation parser allows attackers to crash the application by processing a crafted .scad file. The getComment loop searches the fulltext buffer for a newline but does not stop at the buffer length when the final annotation lacks one. Triggering requires a user or automated workflow to process an attacker-supplied local file; the demonstrated result is a segmentation fault, with no write primitive reported.
Summary
What happened
Out-of-bounds read in OpenSCAD's annotation parser allows attackers to crash the application by processing a crafted .scad file. The getComment loop searches the fulltext buffer for a newline but does not stop at the buffer length when the final annotation lacks one. Triggering requires a user or automated workflow to process an attacker-supplied local file; the demonstrated result is a segmentation fault, with no write primitive reported.
The record
- CVE
- CVE-2022-0497
- Published
- Aug 29, 2022
- Updated
- Aug 2, 2024
- Vendor
- OpenSCAD
- Product
- OpenSCAD
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=Not-Known.
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.
Public exploit references
- oobr_comment.scad 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