Repository navigation
chore(deps): suppress block-buffer finding in the Tauri lockfile - #3524
Merged
jpgough-ms merged 1 commit intoOct 27, 2026
Merged
Conversation
OSV now normalises crate names, so GHSA-qwgh-2vcv-g2f7 (filed as block_buffer) matches block-buffer 0.10.4 and fails every scan. The flaw is in the inline cursor that 0.11.0-pre added. Version 0.10 keeps the cursor in a separate field, so the advisory range is too wide. No Tauri release moves to sha2 0.11, so suppress the finding with a VEX statement.
jpgough-ms
approved these changes
Oct 27, 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.
Description
Since 2026-10-27 03:31 UTC, the
osv-scannercheck fails on every PR. OSV started to normalise crate names in production (google/osv.dev#6237). GHSA-qwgh-2vcv-g2f7 names the crateblock_buffer, so it now matchesblock-buffer@0.10.4in the TauriCargo.lock(CVSS 6.3). The advisory, scanner version and lockfile did not change. The next scan ofmainwill also fail. OSV Fix changes only npm packages, so it cannot fix this finding.The finding is a false positive. The flaw is in the cursor that block-buffer 0.11.0-pre and later keep inside the buffer block. 0.10.4 keeps the cursor in a separate field, which a caught panic does not change. The advisory range (
< 0.12.1) is too wide. An update is not possible: the fix (0.12.1) needsdigest0.11, andtauri-codegen2.7.4 andwry0.57.1 still requiresha2 ^0.10.This PR adds the suppression to
osv-scanner.tomland anot_affectedVEX statement (vulnerable_code_not_present). VEX goes from version 14 to 15.block-bufferis only inCargo.lock, so the suppression cannot hide another copy.After this merges, open PRs need Update branch or a new push. A re-run of the check uses the old merge commit, which has the old
osv-scanner.toml.Not in this PR: a request to GitHub to correct the advisory range to
>= 0.11.0-pre, < 0.12.1. When OSV has the correct range, the suppression can be removed.Type of Change
Affected Components
cli/)calm/)calm-ai/)calm-hub/)calm-hub-ui/)calm-lab/)calm-models/)calm-server/)calm-studio/)calm-widgets/)calm-guard/)docs/)shared/)calm-plugins/vscode/)Commit Message Format ✅
chore(deps): suppress block-buffer finding in the Tauri lockfileTesting
I have tested my changes locally
I have added/updated unit tests
All existing tests pass
osv-scannerv2.6.0 with the CI flags and all four lockfiles: with themainconfig, 1 finding at or above CVSS 5 (this one). With this branch, 0. The other 6 findings are the known Cargo findings below the threshold.I compared the source of block-buffer 0.10.4, 0.11.0-pre and 0.12.1 to confirm where each version keeps the cursor.
No code changed, so the test suites were not run.
Checklist