[GHSA-h5x4-m2qf-r4f2] Diesel's SQLite backend has possible UTF-8 corruption#7674
Open
weiznich wants to merge 1 commit into
Open
[GHSA-h5x4-m2qf-r4f2] Diesel's SQLite backend has possible UTF-8 corruption#7674weiznich wants to merge 1 commit into
weiznich wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
weiznich/advisory-improvement-7674
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the GitHub-reviewed advisory record for GHSA-h5x4-m2qf-r4f2 (Diesel SQLite UTF-8 corruption) to reflect revised severity classification metadata (CVSS v4 vector, CWE list, and GitHub “severity”).
Changes:
- Updates the CVSS v4 vector (notably
ATand impact metrics). - Removes the previously assigned CWE (
CWE-89) and setscwe_idsto an empty list. - Lowers
database_specific.severityfromHIGHtoLOW.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
10
to
13
| { | ||
| "type": "CVSS_V4", | ||
| "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N" | ||
| "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N" | ||
| } |
Author
There was a problem hiding this comment.
I don't think this correct, given the requirements to trigger this at all.
weiznich
commented
May 12, 2026
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.
Updates
Comments
This is no SQL injection, but an broken safety invariant while deserializing data coming from the database.
Any attacker would need to have arbitrary write access to the database so that they can insert arbitrary binary data into a column where the application code using diesel expects an UTF-8 string. That usually requires that the attacker circumvents the normal way to insert data into this field as it can be assumed that almost always a string (that is utf-8) is used for that purpose. Based on this I suggest to change Attack Requirements (AT) to present and also Integrity to none (as there is no way that I'm aware of to use this to actually modify data as everything happens during deserialization)