{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28595 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28595 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28595 is a high-severity memory corruption vulnerability in Prusa Research, published on 10 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-28595 and fix it if it is affected.\n\nWhat it is: CVE-2020-28595 is a high-severity memory corruption vulnerability in Prusa Research, published on 10 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-28595 in the wild and no public exploit code.\n\nAffected product: Prusa Research. 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-2020-28595/ (Markdown: https://insights.sbomify.com/CVE-2020-28595/index.md)","id":"CVE-2020-28595","markdown":"https://insights.sbomify.com/CVE-2020-28595/index.md","name":"CVE-2020-28595","record":{"aliases":["DEBIAN-CVE-2020-28595","GHSA-m2f3-4gc2-3wcw","UBUNTU-CVE-2020-28595"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"3D printing slicer","requires_auth":"none","summary":"An attacker can execute arbitrary code by tricking a user into opening a specially crafted OBJ file in PrusaSlicer.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"prusaslicer","vendor":"prusa3d"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"An out-of-bounds write vulnerability exists in the Obj.cpp load_obj() functionality of Prusa Research PrusaSlicer 2.2.0 and Master (commit 4b040b856). A specially crafted obj file can lead to code execution. 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 Prusa Research","id":"CVE-2020-28595","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Prusa Research","id":"CVE-2020-28596"},"packages":[],"prev":{"headline":"Use after free in Prusa Research","id":"CVE-2020-28594"},"products":["Prusa Research"],"published":"2021-02-10","related":[{"cvss_score":8.8,"headline":"Use after free in Prusa Research","id":"CVE-2020-28594","kev_date_added":null,"published":"2021-08-17"},{"cvss_score":8.8,"headline":"Memory corruption in Prusa Research","id":"CVE-2020-28598","kev_date_added":null,"published":"2021-07-08"},{"cvss_score":8.8,"headline":"Memory corruption in Prusa Research","id":"CVE-2020-28596","kev_date_added":null,"published":"2021-02-10"},{"cvss_score":5.3,"headline":"Command injection in n/a","id":"CVE-2023-47268","kev_date_added":null,"published":"2026-05-08"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can execute arbitrary code by tricking a user into opening a specially crafted OBJ file in PrusaSlicer.","url":"https://insights.sbomify.com/CVE-2020-28595/"}