dbcve.org
RusqliteDatabase / datastore · Rusqlite Project

CVE-2020-35867

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-31
Fix available
A fix is available. Upgrade to 0.23.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via create_module.

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

Memory safety vulnerability in rusqlite crate before 0.23.0 allows memory corruption via the create_module function, enabling potential arbitrary code execution or denial of service.

MitigationUpgrade rusqlite to version 0.23.0 or later. If using create_module, audit custom module implementations for memory safety issues before upgrading.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RusqliteDatabase / datastore
Affected:< 0.23.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Locate rusqlite version in your project
    Inspect your Cargo.lock file and search for the rusqlite entry, or check your Cargo.toml dependencies for the specified version
    Affected if The rusqlite version listed is less than 0.23.0
  2. Verify create_module function usage
    Search your Rust source code for occurrences of 'create_module' function calls
    Affected if Your code calls the create_module function from rusqlite
  3. Confirm the vulnerability condition
    Cross-reference: if rusqlite version is below 0.23.0 AND create_module is called in your code, the environment is affected
    Affected if Both conditions are true: rusqlite < 0.23.0 AND create_module is used

You are affected if your project uses rusqlite with a version lower than 0.23.0 and also utilizes the create_module function.

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.

dbcve · scoped
Upgrade available Upgrade to 0.23.0 or later
Fixed in 0.23.0
Interim mitigation

Upgrade rusqlite to version 0.23.0 or later. If using create_module, audit custom module implementations for memory safety issues before upgrading.

Recommended fix High confidence

0.23.0

  1. Update the rusqlite dependency in your Cargo.toml file to version 0.23.0 or later (e.g., rusqlite = "0.23.0")
  2. Run `cargo update` to fetch the updated crate version
  3. Run `cargo build` to rebuild with the fixed version
  4. Test your application to verify functionality remains intact
Caveat Minor version upgrade - review release notes for any API changes; test thoroughly before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rusqlite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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