Heap overwrite via stale cloned facet capacity
Published Apr 20, 2023 · Updated Aug 3, 2024
Heap-based buffer overflow in Slic3r libslic3r 1.3.0 and Master Commit b1a5500 allows attackers to corrupt memory via a crafted STL file. TriangleMesh::clone allocates facet_start for number_of_facets but retains the larger facets_malloced value; stl_add_facet then skips reallocation and writes beyond the smaller allocation. Processing the file is required, and the demonstrated consequence is an AddressSanitizer-detected crash during mesh repair.
Summary
What happened
Heap-based buffer overflow in Slic3r libslic3r 1.3.0 and Master Commit b1a5500 allows attackers to corrupt memory via a crafted STL file. TriangleMesh::clone allocates facet_start for number_of_facets but retains the larger facets_malloced value; stl_add_facet then skips reallocation and writes beyond the smaller allocation. Processing the file is required, and the demonstrated consequence is an AddressSanitizer-detected crash during mesh repair.
The record
- CVE
- CVE-2022-36788
- Published
- Apr 20, 2023
- Updated
- Aug 3, 2024
- Vendor
- Slic3r
- Product
- libslic3r
- Classifications
- CWE-787, CWE-130
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 20, 2023CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.3.0
- Affected versionversion=Master Commit b1a5500
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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