fix(deps): dependabot remediation 2026-07-16 (tkhq/qos) - #766
Open
arawal wants to merge 1 commit into
Open
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
Auto-opened by the Dependabot remediation workflow.
serde_with 3.11.0 → 3.21.0 (lockfile-only)
Covers alerts:
src/init/Cargo.lock)src/qos_enclave/Cargo.lock)Cargo.lock)Advisory: GHSA-7gcf-g7xr-8hxj — medium severity
Actual severity: informational · Complexity: trivial · Score: 60
What changed
v3.11.0 → v3.21.0 patches a DoS panic in the
KeyValueMapserializer, which subtracted1from the caller-visible length before validating that an inner sequence/map entry contained the required first key field (fixed in upstream PR #966; commit c8a1d82). No API changes.Reachability
Taking the patch defensively; the vulnerable code path is unreachable in
tkhq/qosbecause there are zero uses ofKeyValueMapor#[serde_as(...)]in this repo's source.serde_withis a transitive-only dep pulled in viaaws-nitro-enclaves-cose 0.5.2(COSE signing helpers) andbollard-stubs(Docker API stubs).Required by upstream
serde_with
3.21.0's own manifest requires:serde_with_macros = 3.21.0(exact match, proc-macro sub-crate — bumped in lockstep)serde_core ^1.0.225(new hard normal dep)serde_json ^1.0.145(forcedserde_json 1.0.143→1.0.150)serde_withenable in this workspace:bs58 ^0.5.1,schemars ^0.9.0,schemars ^1.0.2Cascading forced transitives:
darling 0.20.11 → 0.23.0(required byserde_with_macros 3.21.0), which also lockstep-bumpsdarling_coreanddarling_macrodyn-clone,ref-cast,ref-cast-impl,zmij,tinyvec,tinyvec_macros(added transitively byschemars/serde_json 1.0.150/bs58)fnv,ryuremoved (no longer required by the new versions)Note on
src/init/Cargo.lockThis lockfile had pre-existing workspace drift from
chore: release v0.12.2(commit 7097d23) which bumped[workspace.package] versionin the root manifest but did not refresh this child lockfile. Runningcargo update -p serde_withreconciles that as a side-effect, so this PR also updates the internal workspace path-depsqos_core/qos_crypto/qos_hex/qos_json/qos_nsm/qos_p256from 0.10.0 to 0.12.2. These are internal path-deps (not external supply-chain changes) and were required to keep the lockfile consistent with the workspace manifest.