Update Rust crate diesel to v2.3.10 [SECURITY]#480
Open
oxide-renovate[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.3.9→2.3.10Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Diesel has possible use after free when deserializing a SQLite database via
SqliteConnection::deserialize_readonly_databaseGHSA-ggxf-9f6j-w742
More information
Details
Diesel allows loading a SQLite database from a byte buffer, represented as
&[u8], at runtime via theSqliteConnection::deserialize_readonly_databasefunction. In previous versions of Diesel, this buffer was passed directly to libsqlite3. Since libsqlite3 requires the buffer to remain alive for as long as the database connection is open and Diesel did not ensure this as part of its safe API, callers ofSqliteConnection::deserialize_readonly_databasecould drop the buffer prematurely. This prematurely drop caused libsqlite3 to operate on freed memory.This vulnerability affects users of
SqliteConnection::deserialize_readonly_databasewho drop the buffer passed to the function before they drop the database connection.Mitigation
The preferred mitigation to the outlined problem is to update to Diesel version 2.3.10 or newer, which includes a fix for the problem. Alternatively users need to take to keep the buffer alive until the connection is dropped.
Resolution
Diesel now stores a copy of the buffer inside of the
SqliteConnectionobject itself to keep it alive as long as the underlying libsqlite3 connection exists.Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
diesel-rs/diesel (diesel)
v2.3.10Compare Source
diesel print-schemaORDER BYandGROUP BYclausesConfiguration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.