LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28591: An out-of-bounds read vulnerability exists in the AMF File AMFParserContext::endElement() functionality of...

An out-of-bounds read vulnerability exists in the AMF File AMFParserContext::endElement() functionality of Slic3r libslic3r 1.3.0 and Master Commit 92abbc42. A specially crafted AMF file can lead to information disclosure. An attacker can provide a malicious file to trigger this vulnerability.

HighCVSS 8.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-28591 is an information-disclosure flaw in Slic3r's AMF file parsing. A malicious AMF model file can trigger an out-of-bounds read in affected libslic3r versions. Business urgency is highest where 3D-printing workflows accept external or customer-supplied AMF files.

Executive priority

Treat as high priority for organizations operating 3D-printing or model-processing services that handle outside files. For general enterprises without Slic3r/libslic3r exposure, priority is lower after inventory confirms absence.

Technical view

The issue affects Slic3r libslic3r 1.3.0 and master commit 92abbc42 in AMFParserContext::endElement(). The supplied CVSS 3.0 score is 8.6, with high confidentiality impact and no integrity or availability impact. The root weakness is listed as CWE-20 improper input validation.

Likely exposure

Exposure is likely limited to systems using affected Slic3r/libslic3r code to parse AMF files, especially automated upload, conversion, slicing, or print-preparation pipelines that process untrusted model files.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The described trigger is an attacker-provided malicious AMF file processed by the vulnerable parser, leading to possible information disclosure.

Researcher notes

Evidence supports an out-of-bounds read in AMF parsing with confidentiality impact. The source bundle does not provide exploit details, fixed upstream commit, or universal patch version, so remediation should track vendor and distribution advisories.

Mitigation direction

  • Inventory Slic3r and embedded libslic3r usage in print, conversion, and model-processing workflows.
  • Apply available distribution or project updates, including relevant Fedora package advisories where applicable.
  • Restrict AMF ingestion from untrusted users until affected components are updated or removed.
  • Run AMF parsing in isolated, least-privileged processing environments.
  • Check current vendor or package guidance for exact fixed versions.

Validation and detection

  • Confirm whether Slic3r libslic3r 1.3.0 or commit 92abbc42 is present.
  • Map every service or workstation that imports, converts, or slices AMF files.
  • Verify external users cannot submit AMF files to vulnerable processing paths.
  • Confirm updated packages are installed from the relevant OS or application channel.
  • Review logs for unusual parser crashes or failures around AMF processing.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2020-28591 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.6High
CVSS 3.0 vector shape for CVE-2020-28591Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aSlic3rSlic3r libslic3r 1.3.0 , Slic3r libslic3r Master Commit 92abbc42Listed
Weakness

CWE details

CWE-20

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.