RusqliteDatabase / datastore · Rusqlite Project
CVE-2020-35868
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 · uneditedAn issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via UnlockNotification.
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 confidenceThe rusqlite crate (SQLite bindings for Rust) before version 0.23.0 contains a memory safety vulnerability related to UnlockNotification. This is a critical flaw in a low-level database binding that could allow memory corruption or unsafe memory access, potentially enabling arbitrary code execution.
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
< 0.23.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify rusqlite version in dependenciesInspect your Cargo.lock file for the rusqlite entry, or run `cargo tree -p rusqlite` to see the installed versionAffected if The version listed is less than 0.23.0 (e.g., 0.22.0, 0.21.0, etc.)
-
Check Cargo.toml for direct rusqlite dependencyReview your project Cargo.toml for a rusqlite dependency entry and note the specified version range or pinned versionAffected if The version constraint allows versions below 0.23.0 (e.g., "0.22", ">=0.20.0<0.23.0", or any unpinned "*")
-
Verify UnlockNotification feature flag usageSearch Cargo.toml for any enable feature flag referencing unlock_notification (e.g., features = ["unlock_notification"])Affected if The unlock_notification feature is enabled in your rusqlite dependency configuration
-
Detect UnlockNotification API usage in source codeSearch source files for usage of UnlockNotification related APIs such as `unlock_notify`, `SqliteUnlockedNotificationCallback`, or similar patternsAffected if Your codebase directly uses UnlockNotification callback functions or related methods
You are affected if your installed rusqlite version is below 0.23.0 and your application either enables the unlock_notification feature or uses UnlockNotification-related API calls.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.23.0
Upgrade rusqlite to version 0.23.0 or later. Review the application for any usage of UnlockNotification functionality and ensure the upgrade does not introduce breaking changes.
0.23.0
- Update your Cargo.toml file to specify rusqlite version 0.23.0 or later: Change 'rusqlite = "<0.23.0"' to 'rusqlite = "0.23.0"' or use a semver-compatible requirement like 'rusqlite = ">=0.23.0"'
- Run 'cargo update' to fetch the new dependency version
- Run 'cargo build' or 'cargo check' to verify the project compiles with the new version
- Test your application thoroughly to ensure the upgrade does not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rusqlite
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-35868 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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