Security readout for executives and security teams
Plain-English summary
OpenSCAD 2020.12-RC2 has a memory corruption flaw when importing STL files. A malicious STL file could cause code execution if a user opens or imports it. This is mainly a file-handling risk for CAD users who receive models from outside trusted channels.
Executive priority
Treat this as high priority for engineering or CAD environments that handle external models. The business risk is code execution from a file a user opens, not broad internet-wide exposure.
Technical view
CVE-2020-28600 is an out-of-bounds write in OpenSCAD import_stl.cc import_stl(). The CVSS 3.0 score is 8.8 with user interaction required. Sources state a specially crafted STL file can trigger code execution. The provided affected version is OpenSCAD 2020.12-RC2.
Likely exposure
Exposure is most likely where OpenSCAD 2020.12-RC2 is installed and users import STL files from email, shared drives, downloads, customers, vendors, or public model repositories.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires convincing a user or workflow to process a malicious STL file in the affected OpenSCAD version.
Researcher notes
The evidence identifies one affected release candidate and the vulnerable import_stl path. Do not expand scope to other OpenSCAD versions without additional vendor or advisory evidence. No exploit-in-the-wild evidence is provided.
Mitigation direction
- Inventory OpenSCAD installations and identify any 2020.12-RC2 usage.
- Do not import untrusted STL files with affected OpenSCAD builds.
- Check OpenSCAD and Talos guidance for fixed or safe versions.
- Prefer trusted model sources until remediation is confirmed.
- Isolate affected CAD workstations from sensitive systems where practical.
Validation and detection
- Confirm installed OpenSCAD version on CAD and engineering endpoints.
- Review whether users import STL files from external or untrusted sources.
- Check endpoint telemetry for unexpected crashes during STL imports.
- Verify remediation against vendor or Talos guidance before closing.
- Document remaining exceptions and compensating controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-28600 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
8.8HighVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://talosintelligence.com/vulnerability_reports/TALOS-2020-1224CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.