dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-37794

HIGH · 7.5 CVSS v3.1 Published 2024-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation in CVC5 Solver v1.1.3 allows attackers to cause a Denial of Service (DoS) via a crafted SMT2 input file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CVC5 Solver v1.1.3 contains an improper input validation vulnerability that allows attackers to cause denial of service by providing a crafted SMT2 input file. The solver fails to properly validate or sanitize input before processing, allowing malformed SMT2 content to trigger excessive resource consumption or crashes.

MitigationUpdate to a patched version of CVC5 Solver when available, or implement input validation and resource limits on SMT2 file processing to prevent DoS from malformed input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed CVC5 Solver version
    Run 'cvc5 --version' or 'cvc5 -V' from command line to display version information
    Affected if Version displayed is 1.1.3 exactly
  2. Confirm SMT2 file processing capability
    Verify that the CVC5 binary supports SMT2 input by running 'cvc5 --help' and checking for smt2/SMT2 related options
    Affected if SMT2 support is available and enabled in the binary
  3. Review recent CVC5 execution logs
    Check any application logs or terminal output for crashes, segfaults, or excessive resource usage when processing SMT2 files
    Affected if Logs show crashes or abnormal termination when processing SMT2 input
  4. Compare version against affected release
    If version is displayed as v1.1.3 or 1.1.3 (without additional patch suffixes), the exact vulnerable version is present
    Affected if Installed version is 1.1.3 with no later patch applied

You are affected if CVC5 Solver version 1.1.3 is installed and your system processes or can process SMT2 input files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of CVC5 Solver when available, or implement input validation and resource limits on SMT2 file processing to prevent DoS from malformed input.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
22.0 hours of engineering $3,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37794 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data