Memory exhaustion via unreleased extrusion clones
Published Mar 1, 2022 · Updated Jul 9, 2026
Memory leak in Slic3r libslic3r 1.3.0 and master commit b1a5500 allows attackers to exhaust memory via a crafted STL file. PerimeterGenerator::process appends cloned extrusion paths whose allocated copies are not released when the generator is destroyed. Opening or processing the attacker-supplied model is required; the resulting growth depletes available memory and interrupts Slic3r, with no reported data exposure or modification.
Summary
What happened
Memory leak in Slic3r libslic3r 1.3.0 and master commit b1a5500 allows attackers to exhaust memory via a crafted STL file. PerimeterGenerator::process appends cloned extrusion paths whose allocated copies are not released when the generator is destroyed. Opening or processing the attacker-supplied model is required; the resulting growth depletes available memory and interrupts Slic3r, with no reported data exposure or modification.
The record
- CVE
- CVE-2021-44961
- Published
- Mar 1, 2022
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2022CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- Crafted STL memory-exhaustion 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