Compiler crash via unchecked parser null pointer
Published Mar 27, 2024 · Updated Nov 4, 2025
NULL pointer dereference in the MiniZinc parser before 2.8.0 allows local users to crash the compiler with a crafted .mzn file. The ti_expr parser path uses a null pointer before it can throw the intended syntax error for malformed model input. Exploitation requires a local user to invoke the compiler on an attacker-controlled model; the dispute concerns the absence of a common unattended processing use case.
Summary
What happened
NULL pointer dereference in the MiniZinc parser before 2.8.0 allows local users to crash the compiler with a crafted .mzn file. The ti_expr parser path uses a null pointer before it can throw the intended syntax error for malformed model input. Exploitation requires a local user to invoke the compiler on an attacker-controlled model; the dispute concerns the absence of a common unattended processing use case.
The record
- CVE
- CVE-2023-46046
- Published
- Mar 27, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- array2d_bool.mzn crash reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo