CVE-2020-35866 json
Use after free in rusqlite
published 6y ago modified 4mo ago also CVE-2020-35867 , CVE-2020-35868 , CVE-2020-35869 , CVE-2020-35870 , CVE-2020-35871 , CVE-2020-35872 , CVE-2020-35873 , GHSA-28ph-f7gx-fqj8 , GHSA-3cgf-9m6x-pwwr , GHSA-6q5w-m3c5-rv95 , GHSA-8h4j-vm3r-vcq3 , GHSA-8r7q-r9mx-35rh , GHSA-g4w7-3qr8-5623 , GHSA-q3cc-7p7g-392c , GHSA-rjh8-p66p-jrh5 , RUSTSEC-2020-0014 , EUVD-2021-1601
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via VTab / VTabCursor.
Patch / fix
- crates.io rusqlite 0.23.0
- rusqlite_project rusqlite 0.23.0
- github.com/rusqlite/rusqlite@ac30e16 commit
- github.com/rusqlite/rusqlite@2ef3628 commit
- github.com/rusqlite/rusqlite@71b2f51 commit
- github.com/rusqlite/rusqlite@3c6b57f commit
- github.com/rusqlite/rusqlite@2327d3b commit
- github.com/rusqlite/rusqlite@45fd77e commit
- github.com/rusqlite/rusqlite@c9ef5bd commit
- github.com/rusqlite/rusqlite/releases/tag/0.23.0 release
Is CVE-2020-35866 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.74% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | rusqlite | <0.23.0 >=0.0.0-0, <0.23.0 |
0.23.0 |
Classification
References
-
github.com
/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6
web
-
github.com
/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3
web
-
github.com
/rusqlite/rusqlite/commit/71b2f5187b0cbace3f8b6ff53432ff2ca0defcf0
web
-
github.com
/rusqlite/rusqlite/commit/3c6b57fe1b2cc87e7ebecde43dd836ffb1c4ea5c
web
-
github.com
/rusqlite/rusqlite/commit/2327d3b774927fdf48903c0bdc1ca7ec93c7c8d0
web
-
github.com
/rusqlite/rusqlite/commit/45fd77ee43c38eea4d6f4e2e56c1667a55ec654f
web
-
github.com
/rusqlite/rusqlite/commit/c9ef5bd63cad5c0c123344c072b490a1a9bcbe1f
web
-
rustsec.org
/advisories/RUSTSEC-2020-0014.html
web, third-party-advisory, advisory
-
github.com
/rusqlite/rusqlite/releases/tag/0.23.0
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35873
advisory
-
github.com
/rusqlite/rusqlite
package
-
nvd.nist.gov
/vuln/detail/CVE-2020-35870
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35872
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35867
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35871
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35869
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35868
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-35866
advisory
-
crates.io
/crates/rusqlite
package
Sources
- CVE List CVE-2020-35866
- GitHub Advisory GHSA-q3cc-7p7g-392c
- GitHub Advisory GHSA-8h4j-vm3r-vcq3
- GitHub Advisory GHSA-g4w7-3qr8-5623
- GitHub Advisory GHSA-28ph-f7gx-fqj8
- GitHub Advisory GHSA-rjh8-p66p-jrh5
- GitHub Advisory GHSA-8r7q-r9mx-35rh
- GitHub Advisory GHSA-3cgf-9m6x-pwwr
- GitHub Advisory GHSA-6q5w-m3c5-rv95
- NVD CVE-2020-35866
- OSV RUSTSEC-2020-0014
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.