Code execution via OBJ facet buffer overflow
Published Feb 10, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in PrusaSlicer 2.2.0 and commit 4b040b856 allows attackers to execute code via a crafted OBJ file. The load_obj() conversion loop can increment the facet index twice while allocation uses a lower face count, causing malformed vertex groups to write beyond the heap facet array. Execution requires a user to open the attacker-supplied OBJ file, and successful corruption runs code in the PrusaSlicer process.
Summary
What happened
Heap-based buffer overflow in PrusaSlicer 2.2.0 and commit 4b040b856 allows attackers to execute code via a crafted OBJ file. The load_obj() conversion loop can increment the facet index twice while allocation uses a lower face count, causing malformed vertex groups to write beyond the heap facet array. Execution requires a user to open the attacker-supplied OBJ file, and successful corruption runs code in the PrusaSlicer process.
The record
- CVE
- CVE-2020-28595
- Published
- Feb 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Prusa Research
- Product
- PrusaSlicer
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=Prusa Research PrusaSlicer 2.2.0 ,Prusa Research PrusaSlicer Master (commit 4b040b856)
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