CVE-2021-45847 json
Several missing input validations in the 3MF parser component of Slic3r libslic3r 1.3.0 can each allow an attacker to cause an application…
published 2022-01-25 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-32565
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
Several missing input validations in the 3MF parser component of Slic3r libslic3r 1.3.0 can each allow an attacker to cause an application crash using a crafted 3MF input file.
Patch / fix
- github.com/slic3r/Slic3r/issues/5118 advisory
- github.com/slic3r/Slic3r/issues/5119 advisory
- github.com/slic3r/Slic3r/issues/5120 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2021-45847 updated cvss 5.5
slic3r: NULL pointer dereference in 3MF XML via a crafted 3MF input file
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/slic3r/Slic3r/issues/5118
issue-tracking, mitigation, patch, third-party-advisory
-
github.com
/slic3r/Slic3r/issues/5119
issue-tracking, mitigation, patch, third-party-advisory
-
github.com
/slic3r/Slic3r/issues/5120
issue-tracking, mitigation, patch, third-party-advisory
Sources
- CVE List CVE-2021-45847
- NVD CVE-2021-45847
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.