{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-45846 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-45846 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-45846 is a medium-severity vulnerability in n/a, published on 25 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-45846 and fix it if it is affected.\n\nWhat it is: CVE-2021-45846 is a medium-severity vulnerability in n/a, published on 25 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-45846 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2021-45846/ (Markdown: https://insights.sbomify.com/CVE-2021-45846/index.md)","id":"CVE-2021-45846","markdown":"https://insights.sbomify.com/CVE-2021-45846/index.md","name":"CVE-2021-45846","record":{"aliases":["DEBIAN-CVE-2021-45846","GHSA-p759-2vgj-jpmp","UBUNTU-CVE-2021-45846"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"3D printing slicer","requires_auth":"none","summary":"An attacker can crash the Slic3r application by providing a crafted AMF document with a missing metadata type attribute.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"slic3r","vendor":"slic3r"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"A flaw in the AMF parser of Slic3r libslic3r 1.3.0 allows an attacker to cause an application crash using a crafted AMF document, where a metadata tag lacks a \"type\" attribute.","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":"Null dereference in n/a","id":"CVE-2021-45846","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2021-45847"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2021-45845"},"products":["n/a"],"published":"2022-01-25","related":[{"cvss_score":5.5,"headline":"Null dereference in n/a","id":"CVE-2021-45847","kev_date_added":null,"published":"2022-01-25"}],"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 crash the Slic3r application by providing a crafted AMF document with a missing metadata type attribute.","url":"https://insights.sbomify.com/CVE-2021-45846/"}