dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-37795

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
A segmentation fault in CVC5 Solver v1.1.3 allows attackers to cause a Denial of Service (DoS) via a crafted SMT-LIB input file containing the `set-logic` command with specific formatting errors.

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 · high confidence

A segmentation fault in CVC5 Solver v1.1.3 allows attackers to cause denial of service by providing a crafted SMT-LIB input file with a malformed set-logic command containing specific formatting errors that trigger the crash during parsing.

MitigationUpgrade to a patched version of CVC5 when available; otherwise, implement input validation on the set-logic command parser to reject malformed formatting before processing and add proper error handling to prevent segmentation faults from untrusted 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. Identify CVC5 installation and version
    Run 'cvc5 --version' or check the binary metadata to determine the installed version of CVC5
    Affected if The version is v1.1.3
  2. Verify SMT-LIB input processing is in use
    Inspect application logs, code, or configuration to confirm the CVC5 solver processes SMT-LIB format input files
    Affected if The application parses SMT-LIB input files using CVC5
  3. Confirm set-logic command parsing is enabled
    Review whether the application or tool invokes CVC5 with SMT-LIB scripts that may include set-logic commands
    Affected if The solver accepts and processes set-logic commands from external input
  4. Check for untrusted input handling
    Determine if SMT-LIB input files come from untrusted or external sources without prior validation
    Affected if The application processes SMT-LIB input from untrusted sources

The environment is affected if CVC5 version v1.1.3 is installed and processes SMT-LIB input files containing set-logic commands from potentially untrusted sources.

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

Upgrade to a patched version of CVC5 when available; otherwise, implement input validation on the set-logic command parser to reject malformed formatting before processing and add proper error handling to prevent segmentation faults from untrusted input.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37795 — 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-37795 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