{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28600 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-28600 is a high-severity memory corruption vulnerability in Openscad, published on 10 May 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-28600 and fix it if it is affected.\n\nWhat it is: CVE-2020-28600 is a high-severity memory corruption vulnerability in Openscad, published on 10 May 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-28600 in the wild and no public exploit code.\n\nAffected product: Openscad. 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-28600/ (Markdown: https://insights.sbomify.com/CVE-2020-28600/index.md)","id":"CVE-2020-28600","markdown":"https://insights.sbomify.com/CVE-2020-28600/index.md","name":"CVE-2020-28600","record":{"aliases":["DEBIAN-CVE-2020-28600","GHSA-ppjh-5v74-v6qq","UBUNTU-CVE-2020-28600","openSUSE-SU-2021:1024-1","openSUSE-SU-2021:1158-1"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenSCAD CAD software","requires_auth":"none","summary":"An attacker can execute arbitrary code by tricking a user into opening a specially crafted STL file in OpenSCAD.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"openscad","vendor":"openscad"}],"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-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An out-of-bounds write vulnerability exists in the import_stl.cc:import_stl() functionality of Openscad openscad-2020.12-RC2. A specially crafted STL file can lead to code execution. An attacker can provide a malicious file to trigger this vulnerability.","ecosystems":["SUSE:Package Hub 15 SP2","openSUSE:Leap 15.2"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in Openscad","id":"CVE-2020-28600","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in CGAL","id":"CVE-2020-28601"},"packages":[{"ecosystem":"SUSE:Package Hub 15 SP2","fixed":["2019.05-bp152.2.3.1"],"introduced":["0"],"last_affected":[],"package":"openscad","purl":"pkg:rpm/suse/openscad\u0026distro=SUSE%20Package%20Hub%2015%20SP2","source":"openSUSE-SU-2021:1158-1"},{"ecosystem":"openSUSE:Leap 15.2","fixed":["2019.05-lp152.2.3.1"],"introduced":["0"],"last_affected":[],"package":"openscad","purl":"pkg:rpm/opensuse/openscad\u0026distro=openSUSE%20Leap%2015.2","source":"openSUSE-SU-2021:1024-1"}],"prev":{"headline":"Memory corruption in Openscad","id":"CVE-2020-28599"},"products":["Openscad"],"published":"2021-05-10","related":[{"cvss_score":7.1,"headline":"Memory corruption in openscad","id":"CVE-2022-0497","kev_date_added":null,"published":"2022-08-29"},{"cvss_score":5.5,"headline":"Memory corruption in openscad","id":"CVE-2022-0496","kev_date_added":null,"published":"2022-08-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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 STL file in OpenSCAD.","url":"https://insights.sbomify.com/CVE-2020-28600/"}