{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28590 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28590 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28590 is a high-severity vulnerability in Slic3r, published on 13 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-28590 and fix it if it is affected.\n\nWhat it is: CVE-2020-28590 is a high-severity vulnerability in Slic3r, published on 13 Apr 2021. 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-2020-28590 in the wild and no public exploit code.\n\nAffected product: Slic3r. 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-28590/ (Markdown: https://insights.sbomify.com/CVE-2020-28590/index.md)","id":"CVE-2020-28590","markdown":"https://insights.sbomify.com/CVE-2020-28590/index.md","name":"CVE-2020-28590","record":{"aliases":["DEBIAN-CVE-2020-28590","GHSA-6275-8j43-765j","UBUNTU-CVE-2020-28590"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"3D printing slicer","requires_auth":"none","summary":"An attacker can disclose sensitive information by tricking a user into opening a specially crafted OBJ file in Slic3r.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"libslic3r","vendor":"slic3r"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An out-of-bounds read vulnerability exists in the Obj File TriangleMesh::TriangleMesh() functionality of Slic3r libslic3r 1.3.0 and Master Commit 92abbc42. A specially crafted obj file could lead to information disclosure. 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":"Information disclosure in Slic3r","id":"CVE-2020-28590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Slic3r","id":"CVE-2020-28591"},"packages":[],"prev":{"headline":"Integer overflow in tinyobjloader","id":"CVE-2020-28589"},"products":["Slic3r"],"published":"2021-04-13","related":[{"cvss_score":8.1,"headline":"Memory corruption in libslic3r","id":"CVE-2022-36788","kev_date_added":null,"published":"2023-04-20"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can disclose sensitive information by tricking a user into opening a specially crafted OBJ file in Slic3r.","url":"https://insights.sbomify.com/CVE-2020-28590/"}