# CVE-2023-46046: Null dereference in n/a

> A crafted .mzn file can cause a NULL pointer dereference in MiniZinc, leading to a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-46046, GHSA-3gf3-x9x8-839v

## What is CVE-2023-46046?

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.

### Official 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-46046?


## How do I fix CVE-2023-46046?

Upgrade to a fixed version.

## Is CVE-2023-46046 being exploited?

There is no known exploitation of CVE-2023-46046 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46046 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2023-46046 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-46046/ (Markdown: https://insights.sbomify.com/CVE-2023-46046/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46046
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46046
- OSV: https://osv.dev/vulnerability/CVE-2023-46046

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-46046/
Summaries are generated and may contain mistakes; the official description above is the record.