{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-46046 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-46046 is a medium-severity vulnerability in n/a, published on 27 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-46046 and fix it if it is affected.\n\nWhat it is: CVE-2023-46046 is a medium-severity vulnerability in n/a, published on 27 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-46046 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-2023-46046/ (Markdown: https://insights.sbomify.com/CVE-2023-46046/index.md)","id":"CVE-2023-46046","markdown":"https://insights.sbomify.com/CVE-2023-46046/index.md","name":"CVE-2023-46046","record":{"aliases":["DEBIAN-CVE-2023-46046","GHSA-3gf3-x9x8-839v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MiniZinc constraint solver","requires_auth":"low_privilege","summary":"A crafted .mzn file can cause a NULL pointer dereference in MiniZinc, leading to a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"An issue in MiniZinc before 2.8.0 allows a NULL pointer dereference via ti_expr in a crafted .mzn file. NOTE: this is disputed because there is no common libminizinc use case in which an unattended process is supposed to run forever to process a series of atttacker-controlled .mzn files.","ecosystems":[],"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":"Null dereference in n/a","id":"CVE-2023-46046","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Code injection in n/a","id":"CVE-2023-46047"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-46045"},"products":["n/a"],"published":"2024-03-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-11-04","vendors":["n/a"]},"summary":"A crafted .mzn file can cause a NULL pointer dereference in MiniZinc, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2023-46046/"}