{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36788 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36788 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36788 is a high-severity memory corruption vulnerability in libslic3r, published on 20 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36788 and fix it if it is affected.\n\nWhat it is: CVE-2022-36788 is a high-severity memory corruption vulnerability in libslic3r, published on 20 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36788 in the wild and no public exploit code.\n\nAffected product: libslic3r. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-36788/ (Markdown: https://insights.sbomify.com/CVE-2022-36788/index.md)","id":"CVE-2022-36788","markdown":"https://insights.sbomify.com/CVE-2022-36788/index.md","name":"CVE-2022-36788","record":{"aliases":["DEBIAN-CVE-2022-36788","GHSA-c4jg-97gh-363x","UBUNTU-CVE-2022-36788"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"3D printing library","requires_auth":"none","summary":"A heap-based buffer overflow in Slic3r libslic3r allows attackers to execute arbitrary code or cause denial of service via a malicious STL file.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"libslic3r","vendor":"slic3r"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-130","name":"Improper Handling of Length Parameter Inconsistency"}],"description":"A heap-based buffer overflow vulnerability exists in the TriangleMesh clone functionality of Slic3r libslic3r 1.3.0 and Master Commit b1a5500. A specially-crafted STL file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in libslic3r","id":"CVE-2022-36788","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Intel(R) NUC 10 Performance Kits and Intel(R) NUC 10 Performance Mini PCs","id":"CVE-2022-36789"},"packages":[],"prev":{"headline":"webvendome - webvendome SQL Injection","id":"CVE-2022-36787"},"products":["libslic3r"],"published":"2023-04-20","related":[{"cvss_score":8.6,"headline":"Information disclosure in Slic3r","id":"CVE-2020-28590","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2021-44961","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2021-44962","kev_date_added":null,"published":"2022-03-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Slic3r"]},"summary":"A heap-based buffer overflow in Slic3r libslic3r allows attackers to execute arbitrary code or cause denial of service via a malicious STL file.","url":"https://insights.sbomify.com/CVE-2022-36788/"}