RusqliteDatabase / datastore · Rusqlite Project
CVE-2020-35871
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 an Auxdata API data race.
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 confidenceA data race vulnerability exists in the rusqlite Rust library's Auxdata API before version 0.23.0. The race condition can lead to memory safety violations, potentially allowing attackers to cause undefined behavior or memory corruption through concurrent access patterns.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Check the installed rusqlite versionInspect your Cargo.lock file for the rusqlite entry, or run 'cargo tree -p rusqlite' to see the exact version in use. Alternatively, query the library at runtime if your application logs dependencies.Affected if The version listed is any version before 0.23.0 (e.g., 0.22.0, 0.21.0, etc.)
-
Identify if the Auxdata API is used in your codebaseSearch your source code for references to auxdata functions: look for 'auxdata', 'get_aux', 'set_aux', 'remove_aux', or 'with_aux' in your Rust source files.Affected if Any of these Auxdata API functions are present and called in your code
-
Check for concurrent access to database connectionsReview your code for multi-threaded use of the same rusqlite Connection or Statement objects. Look for patterns like spawning threads that share connection handles, using rayon, tokio with concurrent database calls, or std::thread::spawn involving database operations.Affected if Multiple threads or async tasks access the same Connection or Statement object without explicit synchronization around Auxdata operations
-
Inspect thread safety configurationCheck your rusqlite Connection establishment: look for calls to 'Connection::open' or 'Connection::open_in_memory' and whether the ' rusqlite::Connection::batch_execute' or any configuration that enables concurrent access is used.Affected if Connections are used across threads and no thread-local storage or connection pooling with separate connections per thread is implemented
You are affected if your installed rusqlite version is below 0.23.0 AND your code uses the Auxdata API with concurrent access patterns to the same connection or statement object from multiple threads.
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.
From vendor data0.23.0
Upgrade rusqlite to version 0.23.0 or later. If the Auxdata API is used, review thread-safety guarantees and ensure proper synchronization around auxdata operations.
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-35871 — 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-35871 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