Security readout for executives and security teams
Plain-English summary
This flaw affects Slic3r libslic3r OBJ file handling. A malicious OBJ file can trigger an out-of-bounds read and may expose information from the affected process. Priority is highest where Slic3r processes user-supplied or externally sourced 3D model files.
Executive priority
Prioritize remediation for public-facing, customer-facing, or automated 3D file processing environments. Lower priority may be reasonable for isolated desktop use with trusted files only, but the confidentiality impact keeps this above routine maintenance.
Technical view
CVE-2020-28590 is an out-of-bounds read in Obj File TriangleMesh::TriangleMesh() in Slic3r libslic3r 1.3.0 and master commit 92abbc42. It is classified as CWE-20 and scored CVSS 8.6, with confidentiality impact and no integrity or availability impact stated in the bundle.
Likely exposure
Exposure is likely where Slic3r libslic3r 1.3.0 or commit 92abbc42 imports OBJ files, especially from users, customers, or public sources. The bundle provides no CPEs, so inventory requires package, source, or binary checks.
Exploitation context
The bundle says an attacker can provide a malicious OBJ file to trigger the issue. It does not cite active exploitation, and CISA KEV status is false. No exploit steps or weaponized details are needed to assess risk.
Researcher notes
The public bundle identifies the affected function, versions, vulnerability class, and confidentiality impact, but does not include CPEs or a named fixed release. Avoid assuming broader Slic3r forks or downstream products are affected without confirming code lineage.
Mitigation direction
- Check Slic3r upstream and Talos guidance for fixed versions or recommended remediation.
- Restrict or disable untrusted OBJ file processing until remediation is confirmed.
- Isolate file conversion or slicing workflows that handle external 3D model files.
- Treat externally supplied OBJ files as untrusted input in intake workflows.
- Document compensating controls if a fixed build is unavailable.
Validation and detection
- Inventory systems and applications using Slic3r libslic3r 1.3.0 or commit 92abbc42.
- Identify workflows that import OBJ files from users or external parties.
- Confirm whether the deployed build includes a vendor-recognized fix.
- Review logs and intake records for unexpected OBJ processing paths.
- Verify compensating controls block or isolate untrusted OBJ handling.
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-20: 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 lookupCVE-2020-28590 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.6 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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:N/S:C/C:H/I:N/A:N3.94Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
8.6HighVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://talosintelligence.com/vulnerability_reports/TALOS-2020-1213CVE 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 Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.